zuul-jobs/roles/push-to-intermediate-registry/README.rst
Clark Boylan 23826e05a6 Only alias docker registries on test nodes
Skopeo has problems with ipv6 address literals just like docker as they
use the same underlying checks for url validity. However, we think we
can fix that by using a port forward from the executor to the buildset
registry so that skopeo can connect via ipv4

Go back to aliases the registries on test nodes via /etc/hosts.

Change-Id: I5f9316ffe84de06cb2fb2b65a7e1c31d9f8b0e35
Co-Authored-By: James E. Blair <jeblair@redhat.com>
2019-04-22 10:37:33 -07:00

1.8 KiB

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