This disables the upgrade testing temporarily with the intention of
adding it back again when we build 3.7 images and can test the 3.6 to
3.7 upgrade.
Change-Id: I102795248ab9e692e4558257d94d5b3e0b73267e
These images have a number of issues we've identified and worked
around. The current iteration of this change is essentially
identical to upstream but with a minor tweak to allow the latest
mailman version, and adjusts the paths for hyperkitty and postorius
URLs to match those in the upstream mailman-web codebase, but
doesn't try to address the other items. However, we should consider
moving our fixes from ansible into the docker images where possible
and upstream those updates.
Unfortunately upstream hasn't been super responsive so far hence this
fork. For tracking purposes here are the issues/PRs we've already filed
upstream:
https://github.com/maxking/docker-mailman/pull/552https://github.com/maxking/docker-mailman/issues/548https://github.com/maxking/docker-mailman/issues/549https://github.com/maxking/docker-mailman/issues/550
Change-Id: I3314037d46c2ef2086a06dea0321d9f8cdd35c73
Gerrit made new releases and we should update to them. Release notes can
be found here:
https://www.gerritcodereview.com/3.5.html#354https://www.gerritcodereview.com/3.6.html#363
The main improvement for us is likely to be the copy approvals
performance boosts and error handling. We still need to run that prior
to our 3.6 upgrade.
Note we currently only run 3.5 in production but we test the 3.6 upgrade
from our current production version so it makes sense to update the 3.6
image as well.
Change-Id: Idf9a16b443907a2d0c19c1b6ec016f5d16583ad2
Python 3.11 has been released. Once the parent commit of this commit
lands we will have removed our python3.8 images making room for
python3.11 in our image list. Add these new images which will make way
for running and testing our software on this new version of python.
Change-Id: Idcea3d6fa22839390f63cd1722bc4cb46a6ccd53
This was missed in the effort to push out Gerrit 3.5.3 as well as the
ssh rsa sha2 fixes. That said it should be mostly fine as all of the
plugins tagged 3.5.2 have tagged the same commit with 3.5.3. Making this
largely a bookkeeping change.
There is one bit that isn't strictly bookkeeping and that is the
plugins/its-base checkout. Against gerrit 3.5 we convert from a master
checkout [0] to a stable-3.5 [1] checkout as this branch exists now.
Against gerrit 3.6 we convert from a stable-3.6 checkout to a master
checkout. I suspect that a stable-3.6 branch existed for a short period
of time and was cleaned up and zuul is using an old cached state.
The change for its-base on gerrit 3.5 does represent a reversion of
three commits but they all seem related to gerrit 3.6 so I expect this
is fine.
[0] https://gerrit.googlesource.com/plugins/its-base/+log/refs/heads/master
[1] https://gerrit.googlesource.com/plugins/its-base/+log/refs/heads/stable-3.5
Change-Id: I619b28fe642ca8b57eb533157ec0a441f6b66890
It is a good idea ot periodically update our base python images. Now is
a good time to do it as we've got debian bullseye updates and python
minor releases. The bullseye updates fix a glibc bug that was affecting
Ansible in the zuul images. With this update we'll be able to remove the
workaround for that issue.
We also update the builder image's apt-get process to include a clean to
match tbe base image. This is more for consistency than anything else.
Finally update job timeouts for builds as it seems we occasionally need
more time particularly for emulated arm64 builds.
Change-Id: I31483ff434f19f408aef3b63cb2cd24044a8bf29
This adds Gerrit 3.6 image build jobs as well as CI testing for this
version of Gerrit. Once we've got images that build and function
generally we'll reenable the upgrade job and work through that.
Change-Id: I494a21911a2279228e57ff8d2b731b06a1573438
This removes our Gerrit 3.4 image builds as well as testing. We should
land this after an appropriate amount of time has passed since the 3.5
upgrade that we are unlikely to revert.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/847057
Change-Id: Iefa7cc1157311f0239794b15bea7c93f0c625a93
3.4.5 is a fairly minor update. Some bugs are fixed and jgit is updated.
3.4.5 release notes:
https://www.gerritcodereview.com/3.4.html#345
3.5.2 is a bigger update and important adds support for being able to
upgrade to 3.6.0 later. There is a new copy-approvals command that must
be run offline on 3.5.2 before upgrading to 3.6.0. This copies approvals
in the notedb in a way that 3.6.0 can handle them apparently. The
release notes indicate this may take some time to run. We don't need to
run it now though and instead need to make note of it when we prepare
for the 3.6.0 upgrade.
3.5.2 release notes:
https://www.gerritcodereview.com/3.5.html#352
For now don't overthink things and instead just get up to date with our
images.
Change-Id: I837c2cbb09e9a4ff934973f6fc115142d459ae0f
Now that we've cleaned up the old unused images we can look forward to
new Python. Add Python 3.10 base images based on Bullseye.
As part of this process we update the default var values in our
Dockerfiles to set Bullseye and Python3.10 as our defaults as these
should be valid for some time. We also tidy up some yaml anchor names to
make future copy and paste for new versions of images easier to perform
text replacement on.
Change-Id: I4943a9178334c4bdf10ee5601e39004d6783b34c
Everything is running on 3.8 or newer which should allow us to remove
the 3.7 images. This reduces the total set before we add python3.10
images and acts as good cleanup.
Change-Id: I2cc02fd681485f35a1b0bf1c089a12a4c5438df3
We've moved onto bullseye for just about everything at this point. It is
possible there are stragglers and the removal of these jobs should flag
them if their dependencies and requirements are set properly. Otherwise
they'll continue to pull the historical builds on docker hub. Either way
we'll either shake them out or they will continue until they can move to
bullseye.
We remove these in preparation for adding python3.10 images which don't
make sense for buster and our total image catalog is getting large
enough that successfully building and promoting this entire set is
getting problematic. A bit of spring cleaning on what we can commit to
before we commit to some new stuff.
Depends-On: https://review.opendev.org/c/opendev/gear/+/838402
Depends-On: https://review.opendev.org/c/opendev/storyboard/+/838403
Change-Id: I58c4d314ca4f4be3f1e17ec267a4c324cabf0c2a
Refstack is running python3.9 jobs now and they appear to be passing.
Update our image to python3.9 so that we are consistently using
python3.9 in as many locations as possible. Maybe one day we can drop
the 3.7 and 3.8 image builds too.
Change-Id: Iadb84f8f3756fe717ab6bcda0303bc23ff69ad6d
Upload is based on build, since it builds and uploads for the
gate. This means we need to add the mirror here too, so that we're
installing docker from the deb mirror.
We convert to https at the same time for both jobs.
Change-Id: Ie1ff253e6cfc3e666a4e6be919a08f3a5d041319
This plugin was updated to accomodate the ${hash} substition in gerrit
gitweb weblinks. We now need this updated version to build Gerrit
successfully but there is no tag for it yet. Just use the branch to
address this.
Change-Id: I4b0fd4ac845cc4289f78aacfa536db4185f12d38
This will build gerrit 3.5 images and run it through our standard Gerrit
testing. Upgrade testing from 3.4 to 3.5 to follow in followup changes.
Change-Id: I76d0389d1455e62b242aad1926b3a09830301801
We've upgraded to 3.4 and don't appear to be reverting. Remove the 3.3
images as they are no longer needed.
Note we comment out the review upgrade testing jobs until we have 3.5
images building.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/827562
Change-Id: I0e3cb81b790ab06c690ed0245526e4f47911c584
Instead of building a local grafana image with grafyaml installed,
use the plain upstream grafana image along with the newly created
separate opendev grafyaml image to run the dashboards.
Depends-On: https://review.opendev.org/780119
Change-Id: If0d584f848f213aeea385885e3decfaee6303de5
Some spring cleaning now that bullseye is available. While we are at it
we fix up the job requires and provides for the related image building
and service testing jobs too.
Change-Id: I8a392e06df66b2e0c85157e61e529bb649d8ad58
The comments around the organization of these plugins wasn't accurate.
Instead of grouping them by git repo state group them by what
functionality they affect.
Change-Id: I6a21574e7079b7ddda520f727bef5562e5999126
This includes the fixes for right to left unicode that we've already
picked up, but now in an official release. It also updates Elasticsearch
support to prevent use with elasticsearch versions that are vulnerable
to log4shell. We don't use elasticsearch with Gerrit so this doesn't
affect us.
Change-Id: Ifbba7391bd16bc20c003293030a71e0ea787d0c7
This is general spring cleaning that we are going to try and do for our
images now that bullseye is out.
Change-Id: Iad8f5b76896b88a6aafbfba0c38d0749b9d5c88f
There are new gerrit releases. This change updates our production 3.3
image to 3.3.8. We also update Our 3.4 image to 3.4.2 to keep up there.
Release notes for both:
https://www.gerritcodereview.com/3.3.html#338https://www.gerritcodereview.com/3.4.html#342
Seems to largely be bugfixes and reindexing improvements.
Change-Id: Iae8aa403b4001937320767d4166a6af2bc89a2ea