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 | ||
| README.rst | ||
Push artifacts to the intermediate registry
This role will push any images built by :zuulbuild-docker-image into an
intermediate registry.
Run this in a trusted post-playbook at the end of a job after the image build.
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.