Merge ~ubuntu-docker-images/ubuntu-docker-images/+git/utils:update-and-check-images into ~ubuntu-docker-images/ubuntu-docker-images/+git/utils:master
Status: | Rejected |
---|---|
Rejected by: | Bryce Harrington |
Proposed branch: | ~ubuntu-docker-images/ubuntu-docker-images/+git/utils:update-and-check-images |
Merge into: | ~ubuntu-docker-images/ubuntu-docker-images/+git/utils:master |
Diff against target: |
391 lines (+379/-0) 2 files modified
software-versions.sh (+229/-0) update-images.sh (+150/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sergio Durigan Junior | Needs Fixing | ||
Lucas Kanashiro | Needs Information | ||
Review via email: mp+398323@code.launchpad.net |
Description of the change
Towards the objective of flagging merge opportunities for OCI image updates, and to assist in mechanizing at least the simpler refreshes, this adds a pair of scripts:
update-images.sh handles the mechanics of updating the Dockerfile, building the image, and running the unit tests for verification. It uploads the images to the packager's dockerhub repos, but does not push the images to production (that's a job for push-images.sh). The packager is also responsible for pushing the git branch and filing the MP.
check-images.sh extracts version numbers from the official images, as well as local images such as generated from update-images.sh. This first version of the script is limited to five packages, so will need further development to make it more broadly useful.
I'm not wedded to these names for the scripts.
These have been developed rather independently from push-images.sh, however there are some similar functional needs between all of them. I expect that the commonly used functionality could be broken out to a shared include file. There are likely other adjustments that can be made to make all the scripts consistent with code style, variable naming, etc. as followup work.
Thanks for the scripts Bryce. I did not take a deep look into your implementation but based on your description I would say that update-images.sh does not need to upload the image to DockerHub under the packager's namespace, you could simply update the image locally and run the tests against the local image. I can see no gain in uploading it to a personal DockerHub repository, do you have a reason to do it?