In https://github.com/adoptium/ci-jenkins-pipelines/pull/611 I made a change to avoid issuing a docker pull to get the dockerfile for RHEL. This is due to the OS being licensed and therefore cannot be redistributed. This was necessary for Linux/s390x where we build on RHEL because CentOS was not available.
The way this was done was to search for rhel in the image name, which is suboptimal (and in fact I have created images with notrhel in the name elsewhere when I wanted to avoid the pull, such as the windows ones) and was never indented to be a permanent solution. We should add a parameter to the pipelines, or have some other mechanism to do the same, to allow the image not to be "pulled". While we want to have all production images uploaded somewhere (location TBC) this would also allow for more rapid local testing of new images on the machines.
Related:
In https://github.com/adoptium/ci-jenkins-pipelines/pull/611 I made a change to avoid issuing a
docker pull
to get the dockerfile for RHEL. This is due to the OS being licensed and therefore cannot be redistributed. This was necessary for Linux/s390x where we build on RHEL because CentOS was not available.The way this was done was to search for
rhel
in the image name, which is suboptimal (and in fact I have created images withnotrhel
in the name elsewhere when I wanted to avoid the pull, such as the windows ones) and was never indented to be a permanent solution. We should add a parameter to the pipelines, or have some other mechanism to do the same, to allow the image not to be "pulled". While we want to have all production images uploaded somewhere (location TBC) this would also allow for more rapid local testing of new images on the machines.