zuul-jobs

History

Use pipefail in some shell commands.  In this case I don't think we
can really be fooled, but not a bad idea to fail if the first command
errors.

Change-Id: I25750c4edfe815af9e9d9ee47639b315e7133aa2

2023-02-03 15:36:25 +11:00

docker

Support multi-arch image builds with docker buildx

2020-05-04 14:02:13 -05:00

docker-siblings

ensure-podman: Use official podman repos for ubuntu

2021-04-01 16:39:00 -04:00

host_vars

Add a registry test job

2019-06-03 09:03:35 -07:00

roles

linters: rename loop variable

2022-07-27 17:06:30 +10:00

vars

Refresh intermediate TLS certs for testing

2020-11-24 11:39:17 -05:00

buildset-registry-k8s-crio-post.yaml

Add cri-o support to use-buildset registry

2020-01-07 07:35:28 -08:00

buildset-registry-k8s-crio.yaml

ansible-lint: use pipefail

2023-02-03 15:36:25 +11:00

buildset-registry-k8s-microk8s.yaml

ansible-lint: use pipefail

2023-02-03 15:36:25 +11:00

buildset-registry-openshift-docker.yaml

ansible-lint: use pipefail

2023-02-03 15:36:25 +11:00

buildset-registry-pre.yaml

Fix buildset-registry test on focal

2021-05-25 16:38:00 +02:00

buildset-registry.yaml

Prevent leaks of buildset registry credentials

2021-06-24 09:56:19 -07:00

test-registry-post.yaml

test-registry-post: collect k8s logs

2022-11-07 12:44:15 +11:00

test-registry-pre.yaml

zuul-jobs-test-registry-docker-* : update to jammy nodes

2023-02-03 15:05:17 +11:00

test-registry.yaml

Prevent leaks of buildset registry credentials

2021-06-24 09:56:19 -07:00