3fa0c21024
If the docker build jobs see that a buildset_registry is defined (i.e., they are running in a job graph where an earlier job ran a buildset registry) automatically use that registry. Change-Id: Ied7730b793a02204921a2e76f8474fcce534ac77 |
||
|---|---|---|
| .. | ||
| README.rst | ||
| credentials.rst | ||
| pre.yaml | ||
| promote.yaml | ||
| run.yaml | ||
| upload.yaml | ||
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:
- :zuul
build-docker-image: Build the images.- :zuul
upload-docker-image: Build and stage the images on dockerhub.- :zuul
promote-docker-image: Promote previously uploaded images.
The :zuulbuild-docker-image job is designed to be used in a
check pipeline and simply builds the
images to verify that the build functions.
The :zuulupload-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 :zuulpromote-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 :zuulbuild-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