zuul-jobs/roles/pull-from-intermediate-registry
James E. Blair a358f21736 Use buildset registry push endpoint
When copying images from the intermediate registry to the buildset
registry, use the new push endpoint of the dual-registry system.

Also, use the push endpoint after a docker build to push the
new image to the buildset registry.

Change-Id: I3a11036bb9fb7cb3457a3d744fa83647c1b1b085
2019-02-21 14:15:45 -08:00
..
tasks Use buildset registry push endpoint 2019-02-21 14:15:45 -08:00
README.rst Add intermediate registry push/pull roles 2019-02-11 17:41:30 -08:00

Pull artifacts from the intermediate registry

This role will pull any artifacts built for changes ahead of this change which have been placed in an intermediate registry into the buildset registry for this buildset.

Run this in a trusted pre-playbook at the start of a job (which, in the case of multiple dependent jobs in a buildset, should be at the root of the job dependency graph).

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.