zuul-jobs/roles/push-to-intermediate-registry
James E. Blair 05d6187825 buildset registry: fix proxy_port error in push/pull roles
This was copy/pasta from the use_buildset_registry role; the
intermediate registry has no proxy_port, and the push/pull operations
don't need to use the proxy buildset registry, so remove both
entries from the docker config.

Change-Id: I7c2d57d027e457f4f093497938574624cd5a444c
2019-03-18 10:15:02 -07:00
..
tasks buildset registry: fix proxy_port error in push/pull roles 2019-03-18 10:15:02 -07:00
README.rst Add intermediate registry push/pull roles 2019-02-11 17:41:30 -08:00

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.