zuul-jobs/roles/push-to-intermediate-registry
Ian Wienand d1e74606bc
push-to-intermediate-registry: look for container_images variable
When used with the container-image roles, the variable is
container_images, not docker_images.

Change-Id: I074f9523aea7d71879f722b88ff7c3e7e45fb90f
2023-03-24 10:35:35 +11:00
..
tasks push-to-intermediate-registry: look for container_images variable 2023-03-24 10:35:35 +11:00
README.rst push-to-intermediate-registry: look for container_images variable 2023-03-24 10:35:35 +11:00

README.rst

Push artifacts to the intermediate registry

This role will push any images built by :zuulbuild-docker-image or :zuulbuild-container-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 :zuulrun-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.