Pulling the "master" libvirt-ci containers does not work anymore,
so we have to switch to the "latest" instead. See also:
https://gitlab.com/libvirt/libvirt/-/commit/5d591421220c850aa64a640
https://gitlab.com/libvirt/libvirt-ci/-/commit/6e3c5ccac77714be70c0
The effects were dormant for a year as the old ':master' tags were
not removed until some weeks ago.
The other Cirrus-CI jobs were already fixed in commit 1d2f2b35bc86b7a1
("gitlab-ci/cirrus: switch from 'master' to 'latest'"), but apparently
nobody noticed the KVM jobs so far that need to be triggered manually.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
.gitlab-ci.d/cirrus.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.d/cirrus.yml b/.gitlab-ci.d/cirrus.yml
index 4671f069c3..8b45f72910 100644
--- a/.gitlab-ci.d/cirrus.yml
+++ b/.gitlab-ci.d/cirrus.yml
@@ -95,7 +95,7 @@ aarch64-macos-14-base-build:
.cirrus_kvm_job:
extends: .base_job_template
stage: build
- image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
needs: []
timeout: 80m
script:
--
2.44.0
