ba4b2c68b9
This reverts commit 05f20a5396b8a1f463129b99bbe23b8b7862afdd. Apparently skopeo is properly cloud native too and doesn't support ipv6 either. I think it is pulling the same docker distribution/reference/regexp.go lib in and using docker's regex. The error we get from skopeo: time="2019-04-10T15:15:48Z" level=fatal msg="Invalid source name docker://[2607:ff68:100:54:f816:3eff:fef2:fc69]:5000/zuul/nodepool:latest: invalid reference format" Change-Id: I6f916574c9f46e8fdd2464465e2b36ecf8719b16
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 :zuul
run-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.