zuul-jobs/roles/push-to-intermediate-registry
James E. Blair cbff0cc355 push-to-registry: handle undefined docker_images
So that this role may be used unconditionally in jobs which may
or may not actually build images, skip the tasks if the
docker_images variable is undefined.

Change-Id: I6ef0c80230de628f86f523878020c82ce81a1e60
2019-02-19 17:49:21 -08:00
..
tasks push-to-registry: handle undefined docker_images 2019-02-19 17:49:21 -08:00
README.rst Add intermediate registry push/pull roles 2019-02-11 17:41:30 -08:00

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 :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.