e69d879cae
We spawn socat processes in the background in buildset registry related roles. Ansible 5 is much better at killing all processes in its session when the task is complete. Work around that by starting socat within a new session with setsid. Change-Id: Iaab17f5d4068be6b08e3d89d2abe80199f0cd654 |
||
|---|---|---|
| .. | ||
| tasks | ||
| vars | ||
| 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" and "socat" 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.