zuul-jobs/roles/run-buildset-registry
David Shrewsbury ce67cef122 run-buildset-registry: Fix python version check
The "Start the buildset registry" task, which uses the
docker_container Ansible module, was failing with:

    "No module named 'requests'"

This is because the earlier package install task was installing
the packages into the wrong python version because the
ansible_python_interpreter value was 'auto' and thus never
included the 'python3' value.

Change-Id: I887fdf8d000c8b916fdab281c531b7c98bdd5ae2
2019-10-31 16:17:27 -04:00
..
defaults Make the buildset registry port configurable 2019-10-28 15:42:29 -07:00
tasks run-buildset-registry: Fix python version check 2019-10-31 16:17:27 -04:00
templates Test buildset registry with k8s and docker 2019-10-28 15:45:39 -07:00
README.rst Make the buildset registry port configurable 2019-10-28 15:42:29 -07:00

Runs a docker 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.