zuul-jobs/roles/run-buildset-registry
Tobias Henkel 5b3d0c3ee2 Allow overriding the buildset registry image
There are cases when a downstream user of run-buildset-registry needs
to use a different image. This can happen e.g. when this has to be
cached in a local registry. To facilitate this use case add the
buildset_registry_image variable that lets the user specify a
different image.

Change-Id: I0cd3bd2f6bcd0ac73609bf37ce99557472e9f3d1
2024-11-14 11:07:10 -05:00
..
defaults Allow overriding the buildset registry image 2024-11-14 11:07:10 -05:00
tasks Allow overriding the buildset registry image 2024-11-14 11:07:10 -05:00
templates Test buildset registry with k8s and docker 2019-10-28 15:45:39 -07:00
README.rst Allow overriding the buildset registry image 2024-11-14 11:07:10 -05:00

Runs a container registry for the use of this buildset.

This may be used for a single job running on a single node, or it may be used at the root of a job graph so that multiple jobs running for a single change can share the registry.

Role Variables

Return Values

Information about the registry.

The host (IP address) of the registry.

The port on which the registry is listening.

The username used to access the registry via HTTP basic auth.

The password used to access the registry via HTTP basic auth.

The (self-signed) certificate used by the registry.