We still have the Zuul Debian package deployed on WMCS instances. That is legacy and should no more be used.
Description
Details
Revisions and Commits
rCICF integration-config | |||
rCICFe9dfc1f66e4d Stop using zuul-cloner in debian-glue jobs |
Event Timeline
Change 556642 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] jjb: rm unused zuul-cloner scm macro
e9dfc1f66e4ded299ff1770d5afa4c5c48b52ebc did the removal of zuul-cloner in debian glue jobs.
Change 556642 merged by jenkins-bot:
[integration/config@master] jjb: rm unused zuul-cloner scm macro
Change 556643 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] jjb: stop using zuul-cloner in scap-beta-deb
Mentioned in SAL (#wikimedia-releng) [2019-12-12T11:16:37Z] <hashar> Manually rebuilding last build of https://integration.wikimedia.org/ci/job/scap-beta-deb/ to generate a scap package without relying on zuul-cloner | https://gerrit.wikimedia.org/r/556643 | T240551
Change 556643 merged by jenkins-bot:
[integration/config@master] jjb: stop using zuul-cloner in scap-beta-deb
The Zuul package is still installed on the three Jessie instances left over:
integration-trigger-01.integration.eqiad.wmflabs |
integration-slave-jessie-1002.integration.eqiad.wmflabs |
integration-slave-jessie-1004.integration.eqiad.wmflabs |
But it is no more used in any Jenkins job. We can get rid of the zuul package installation from puppet then purge the package from those WMCS instances.
Change 556648 had a related patch set uploaded (by Hashar; owner: Hashar):
[operations/puppet@production] ci: remove zuul-cloner package from Jenkins agents
Mentioned in SAL (#wikimedia-operations) [2019-12-12T11:41:27Z] <hashar> Removing zuul package from Jessie CI instances # T240551
Done. Pending Puppet merge https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/556648/
Change 556648 merged by Jbond:
[operations/puppet@production] ci: remove zuul-cloner package from Jenkins agents