c58e2a51dc
The intermediate registry pull role is designed to be used in the same playbook as the run-buildset-registry role, which sets the buildset_registry fact. However, that fact is set on the host where the registry runs, not localhost. Theoretically we should be able to delegate setting that fact to all hosts in the inventory, plus localhost, however, that doesn't seem to work in local testing. Work around this by, once again, loading the buildset_registry fact from the zuul_return file. Change-Id: Ia16b3af8782c875e64ad5eeeeb5f107482a3e30a |
||
|---|---|---|
| .. | ||
| tasks | ||
| README.rst | ||
Pull artifacts from the intermediate registry
This role will pull any artifacts built for changes ahead of this change which have been placed in an intermediate registry into the buildset registry for this buildset.
Run this in a trusted pre-playbook at the start of a job (which, in the case of multiple dependent jobs in a buildset, should be at the root of the job dependency graph).
This requires the :zuulrun-buildset-registry role already applied. It also
requires an externally managed "intermediate" registry operating for the
use of Zuul, and it requires "skopeo" to be installed on the Zuul
executors.
Role Variables
Information about the registry, as returned by :zuul
run-buildset-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.
Information about the registry. This is expected to be provided as a secret.
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.