29d55cbf17
Add support for "siblings:" to the build-container-image role. This is a port of change I079d823e7194e15b1b496aea0f53f70f6b563f02 from the build-docker-image role. Note that we found a couple of issues with this role, fixed with I9f3b0a1f71d20cf7511f224648dd2fa51a039015. However, build-container-image has merged before this fix, so thess fixes now follow this change. To avoid squashing this into something confusing this update incorporates those fixes. However testing is left to the follow-on change because the extant build-docker-image role would fail the corrected testing. They should be merged roughly together. One minor thing is the removal of an additional duplicated "tags:" entry from the variable documentation. Change-Id: I71e2f2ab29446bd113644ce8c75378b8d3ef8ba6
4.7 KiB
This is one of a collection of roles which are designed to work together to build, upload, and promote container images in a gating context:
- :zuul
build-container-image: Build the images.
Note
Build and upload roles are forthcoming.
The :zuulbuild-container-image role is designed to be used in
check and gate pipelines and simply builds the images. It
can be used to verify that the build functions, or it can be followed by
the use of subsequent roles to upload the images to a registry.
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.
Use the :zuulinstall-docker or :zuulinstall-podman role to install Docker or Podman
before using these roles.
Role Variables
The default container filename name to use. Serves as the base for :zuul
build-container-image.container_images.container_filename. This allows a global overriding of the container filename name, for example when building all images from different folders with similarily named containerfiles.If omitted, the default depends on the container command used. Typically, this is
DockerfilefordockerandContainerfile(with a fallback onDockerfile) forpodman.