zuul-registry/playbooks/functional-test
Clark Boylan 7e28263067 Run image builds on noble
This runs our zuul-registry container image builds on noble because we
rely on skopeo being able to talk to docker's daemon but jammy skopeo is
too old to talk to modern docker. Running on noble should get us newer
skopeo can speak to new docker as well. Note we explicitly add
python3-setuptools to the extra packages list because docker-compose
needs it and doesn't explicitly list it as a dependency.

While we are at it we add python3.12 unittesting on noble too.

Change-Id: I3e84b0a5fc9cd29ab8cf510a59ef6bfed8b5abbd
2024-10-30 10:36:44 -07:00
..
conf Disable namespacing 2019-10-21 09:47:41 -07:00
files Disable namespacing 2019-10-21 09:47:41 -07:00
restricted Publish container images to quay.io 2023-04-26 09:59:32 -07:00
cleanup.yaml Add podman buildset test 2019-10-10 16:49:37 -07:00
docker-buildset.yaml Fix and/or matching for image pre-conditions 2022-03-04 06:45:21 +11:00
docker-compose.yaml Publish container images to quay.io 2023-04-26 09:59:32 -07:00
docker.yaml Fix "docker manifest create" issue 2022-04-06 15:37:07 -04:00
localtest.yaml Add podman buildset test 2019-10-10 16:49:37 -07:00
podman-buildset.yaml Fix and/or matching for image pre-conditions 2022-03-04 06:45:21 +11:00
podman.yaml podman: make sure we remove the pulled image 2022-03-04 06:45:21 +11:00
post.yaml Switch to collect-container-logs 2020-01-09 19:42:49 -05:00
restricted.yaml Add more robust testing of the registry 2022-02-28 14:19:03 -08:00
run.yaml Run image builds on noble 2024-10-30 10:36:44 -07:00
setup.yaml Publish container images to quay.io 2023-04-26 09:59:32 -07:00