The zuul-merger git repositories are exposed to the Jenkins slaves via a git-daemon process. The two instances are on contint1001 and contint2001 and each run git 2.1.4 from jessie/main.
git 2.11.0 is available from jessie-backports/main. Potentially we could upgrade git which might benefit git-daemon. No idea about what has changed in git-daemon though.
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| operations/puppet | production | +9 -0 | contint: upgrade git on zuul mergers |
We should upgrade git on the Jessie CI instances as well. One benefit is updating submodules in parallel which would benefit operations/puppet (T166888: CI for operations/puppet is taking too long).
Change 360420 had a related patch set uploaded (by Hashar; owner: Hashar):
[operations/puppet@production] contint1001: upgrade git on zuul mergers
We have it experimental too, cf: T140927: Make git 2.2.0+ (preferably 2.8.x) available
Lets upgrade git on the zuul-merger in production and see what happens. I am not too worried.
Mentioned in SAL (#wikimedia-operations) [2017-08-31T08:57:10Z] <hashar> contint2001 upgrading git, restarting git-daemon and zuul-merger - T161086
Upgraded on contint2001
# apt-get install -t jessie-backports git -V The following packages will be upgraded: git (2.1.4-2.1+deb8u4 => 2.11.0-3~bpo8+1) git-man (2.1.4-2.1+deb8u4 => 2.11.0-3~bpo8+1) # systemctl restart git-daemon
If all goes fine, I will then do contint1001.
Mentioned in SAL (#wikimedia-operations) [2017-08-31T09:04:17Z] <hashar> contint1001 upgrading git, restarting git-daemon and zuul-merger - T161086
Change 360420 merged by Dzahn:
[operations/puppet@production] contint: upgrade git on zuul mergers