Same as T118340
TL;DR would need new Zuul .deb to be pushed to apt.wikimedia.org for Precise/Trusty/Jessie
Last week I finally went to upgrade Zuul to the latest version. It is a tedious process to have the same code base to support all three distributions, most notably the python packages are severely outdated. We went with dh_virtualenv which let us easily embed dependencies in the Zuul packages.
I already upgraded:
- Zuul scheduler and merger instances on gallium (Precise).
- All the CI slaves (Precise/Trusty/Jessie)
Would need to upgrade Zuul on gallium and scandium to catchup with version.
The breakdown is:
| Distro | Component | Package materials | Availability |
|---|---|---|---|
| Precise | precise-wikimedia/thirdparty | https://people.wikimedia.org/~hashar/debs/zuul_2.1.0-60-g1cc37f7-wmf4precise1/ | Published |
| Trusty | trusty-wikimedia/thirdparty | https://people.wikimedia.org/~hashar/debs/zuul_2.1.0-60-g1cc37f7-wmf4trusty1/ | Published |
| Jessie | jessie-wikimedia/thirdparty | https://people.wikimedia.org/~hashar/debs/zuul_2.1.0-60-g1cc37f7-wmf4jessie1/ | Published |
Note how Ubuntu uses main whereas with Jessie we now uses thirdparty.
All three packages are based on the same tarball zuul_2.1.0-60-g1cc37f7.orig.tar.gz which is upstream commit 1cc37f7b469a892cdbd16db6aa1d500a1200c417
There should be no impact on production since the package only tweak zuul-cloner which is not used on production.