zuul-jobs/roles/run-buildset-registry
Clark Boylan 4ed66807a0 Use unique loop vars to avoid conflicts
We have to be careful about avoiding outer loop loop_var conflicts in
ansible. Because the zuul-jobs roles are meant to be reconsumed
elsewhere we should not use 'item' loopvars and instead set them to
something a bit more unique.

We use a zj_ prefix to try and be unique to this repo and document this
convention.

Change-Id: I20b9327a914890e9eafcb2b36dc8c23fb472bc8f
2020-02-04 12:23:36 -08:00
..
defaults use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
tasks Use unique loop vars to avoid conflicts 2020-02-04 12:23:36 -08:00
templates Test buildset registry with k8s and docker 2019-10-28 15:45:39 -07:00
README.rst use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08: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.