OpenDev is preparing to upgrade its Gerrit deployment to 3.9, so
make sure git-review is working with the latest 3.9 point release.
This also requires a newer JDK.
While we're at it, switch from testing with Python 3.11 to 3.12
since that's ending up in more user environments these days.
Also drop unit test jobs that exercise old Python with new Gerrit
and new Python with old Gerrit to simplify the test matrix, because
our Python 3.6 platform lacks new enough Java to support current
Gerrit releases.
And since the Python 3.12 testing uses a platform with newer tools,
remove an unnecessary Git command output assert where the output has
diverged significantly from version to version, trusting that Git
will do what it's asked to do because we're not interested in
testing it for regressions anyway.
Depends-On: https://review.opendev.org/920841
Change-Id: Idb1af841ba68a6f536117ef64f3bec011e905203
This change updates the CI testing for git-review to test with Gerrit
3.4.4 and 3.7.1. This should give us good coverage of new and old Gerrit
behavior when making changes to git-review.
Note we leave 3.4.4 as the default in the test suite for local runs to
try and limit possibility of breaking old Gerrit when adding features to
git-review for new Gerrit.
Change-Id: I4a42eddec1e247cbb0af5e74b8f1cee0ad58a79a
This bumps the newest python version tested to 3.11 and drops testing
for 3.7, 3.8, and 3.9. We only test the lower and upper python version
bounds.
We switch to an ed25519 ssh key instead of rsa because Ubuntu Jammy
defaults to rsa + sha2 and Gerrit 3.4.4 does not understand this. This
results in a golden site version bump.
Change-Id: I3989460575fa9c389233244683318a6cfded68fe
Recent tox releases have put us on a config treadmill. Avoid these
issues entirely by using nox. Nox is a tox alternative that uses
standard tools like pip and should be simpler to use for us.
Change-Id: Ie79845bbed7ca1254aec466bd5219186fefcdac9
The default nodeset has switched from focal to jammy, so we need to pin
the jobs that require focal to the correct nodesets.
Change-Id: I6d8dad4c4a4cbfa3a395b2f8a5e40f6717878a8b
We normally publish documentation updates in the promote pipeline,
using documentation built in the gate. As a result, the published
docs tend to lag behind release events until the next post-release
change lands. Run a separate docs build and publish it on release,
so that release notes and version information included in the
documentation reflect the most recent tag prior to the next change
merging (which for stable projects like this one, could be a while).
Override the tag jobvar to force publication to the branch path
rather than using a version-specific tree.
Change-Id: Ibf1ecfa0420a3c170beb79c14a9a9ef13fea9046
Depends-On: https://review.opendev.org/838525
An upcoming change needs a feature from Git 2.10, which Ubuntu 16.04
LTS lacks. Since Python 3.5 reached end of life with the 3.5.10
release on 2020-09-05, it's been unsupported by its maintainers for
nearly 2 years anyway.
Change-Id: I0369c29baa344c4dc76eaa47b3467b6117eb933c
We now are using focal nodes by default, so we no longer need to
explicitly select those, instead we need bionic for py36+py37.
Change-Id: I0f0f44e57a100420d8e6d2eaec7dbb5d77b654af
As git-review has moved to the "opendev" tenant in OpenDev's Zuul
now, update its jobs to still work there and re-add release jobs
based on similar configuration for the opendev/bindep repository.
Change-Id: I7700ca9369080138122829ab2d4ddf3bbaea7b5f
Depends-On: https://review.opendev.org/777774
