zuul-jobs/roles/push-to-intermediate-registry
Monty Taylor 10cea0b22d Don't try to push images when the build failed
When an image build fails we're still trying to push the image to
the registry. This isn't going to work, as there is no image to
push since the build failed.

Add a check for the job being in a success state for if we're
pushing images. This way we can properly report FAILURE instead of
POST_FAILURE.

Change-Id: Idba5c8997111c6e84b44bc970394b58387519666
2019-07-28 14:07:47 -04:00
..
tasks Don't try to push images when the build failed 2019-07-28 14:07:47 -04:00
README.rst Only alias docker registries on test nodes 2019-04-22 10:37:33 -07: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" 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.