71b7cb0ae5
* In the build-image role, push to the buildset registry if it is defined. * In the intermediate registry push and pull roles, ensure that the buildset registry TLS cert is in place. This is a self-signed cert, and so needs to be written for each run. This happens inside bubblewrap where we have permission to write to /etc, which is an ephemeral volume. Change-Id: I47781d8a7adb93817dfe9266e2f4ad5fd829385c |
||
|---|---|---|
| .. | ||
| tasks | ||
| README.rst | ||
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" 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.