Feature #22559
closed
Review, clean up the division of software on Jenkins images
Description
In arvados-dev as of 4951623dc2a418270b5822ad5da0547a39356ea4, jenkins/packer-images/jenkins-image-with-docker.sh is a bit of a misnomer: it installs Docker, Packer, Ansible, and some Arvados Git stuff. It gets used in the process of building packer-build-jenkins-image-build, packer-build-jenkins-image-arvados-tests, and packer-build-jenkins-image-workbench2-tests. The Ansible playbooks in development replicate this setup to try to minimize the number of things changing at once.
But as far as I can tell this setup is overinclusive for everyone. As far as I can tell:
- packer-build-jenkins-image-build just needs Packer, plugins, and Ansible, not Docker
- The test images just need Docker, not Packer or Ansible
Review and clean this up if possible. Installing each piece of software has been done in a different role, so it should be possible to mix and match them however you need.
Updated by Brett Smith about 2 months ago
- Related to Bug #22579: Have most Jenkins jobs use a single shared image jenkins-image-arvados-tests added
Updated by Brett Smith about 2 months ago
- Status changed from New to Rejected
We are handling this by going in the other direction: instead of narrowing the scope of what's installed on each image, we're going to have a single image with all our dependencies installed. That's #22579.