Bug #22557
closed
Review if Git checkouts on Jenkins images still work in 2025
Description
In arvados-dev as of 4951623dc2a418270b5822ad5da0547a39356ea4, jenkins/packer-images/jenkins-image-common.sh says:
# create a reference repository (bare git repo)
# jenkins will use this to speed up the checkout for each job
cd /usr/src
sudo git clone --mirror git://git.arvados.org/arvados.git
sudo chown jenkins:jenkins arvados.git -R
It is not clear whether or how this works. If you review the console output for Jenkins tests, they do a fresh clone under the /tmp workspace. It would maybe save time if they cloned from /usr/src/arvados.git, but there's no indication they do that.
Similar logic applies to the checkout at /usr/local/arvados-dev.
If the Jenkins jobs don't actually use this, then it probably shouldn't be in the image either. The Packer image build jobs tend to assume that arvados-dev is checked out under /usr/local. Consider reconfiguring these jobs to work the normal way in preparation for removing the checkouts.
Updated by Brett Smith 9 months ago
- Status changed from New to Closed
This got audited and figured out in #22965. Briefly:
- Some Jenkins jobs use
/usr/src/arvados.gitas a reference to reduce network transfers. - This doesn't work for all jobs because if you, e.g., mount your clone inside a Docker container then it can't find the reference repo and things break.
- There is some stray infrastructure that uses the checkouts at
/usr/src/arvadosand/usr/local/arvados-devbut they're being cleaned up to stop doing that.