base-jobs

History

Zuul 7180defa63 Merge "Use pause-buildset-registry role"		2020-03-04 16:47:11 +00:00
..
credentials.rst	Add docker image jobs	2019-02-22 08:50:23 -08:00
pre.yaml	Add test docker image build jobs	2020-02-27 06:54:47 -08:00
README.rst	Add docker image jobs	2019-02-22 08:50:23 -08:00
run.yaml	Use pause-buildset-registry role	2020-02-21 17:35:01 -06:00
upload.yaml	Add docker image jobs	2019-02-22 08:50:23 -08:00

README.rst

This is one of a collection of jobs which are designed to work together to build, upload, and promote docker images in a gating context:

:zuulopendev-build-docker-image: Build the images.

:zuulopendev-upload-docker-image: Build and stage the images on dockerhub.

:zuulopendev-promote-docker-image: Promote previously uploaded images.

The :zuulopendev-build-docker-image job is designed to be used in a check pipeline and simply builds the images to verify that the build functions.

The :zuulopendev-upload-docker-image job builds and uploads the images to Docker Hub, but only with a single tag corresponding to the change ID. This job is designed in a gate pipeline so that the build produced by the gate is staged and can later be promoted to production if the change is successful.

The :zuulopendev-promote-docker-image job is designed to be used in a promote pipeline. It requires no nodes and runs very quickly on the Zuul executor. It simply re-tags a previously uploaded image for a change with whatever tags are supplied by :zuulopendev-build-docker-image.docker_images.tags. It also removes the change ID tag from the repository in Docker Hub, and removes any similar change ID tags more than 24 hours old. This keeps the repository tidy in the case that gated changes fail to merge after uploading their staged images.

They all accept the same input data, principally a list of dictionaries representing the images to build. YAML anchors can be used to supply the same data to all three jobs.

Job Variables