Skip to contentSkip to conversation

.gitlab-ci.d/cirrus.yml: Fix the NetBSD and OpenBSD Cirrus-CI KVM jobs

PATCH In review Thomas Huth 3 participants 3 messages Apr 24, 2024

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 .gitlab-ci.d/cirrus.yml: Fix the NetBSD and OpenBSD Cirrus-CI KVM jobs

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.

---
 .gitlab-ci.d/cirrus.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
.gitlab-ci.d/cirrus.yml +1 -1
index 4671f069c3..8b45f72910 100644
@@ -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:
Signature · 1 line
2.44.0
Reviewed-by on v1 1/1
#1 lore raw
Quoted 8 lines · Thomas Huth

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.

Quoted 8 lines

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.

---
 .gitlab-ci.d/cirrus.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

With regards,
Daniel

Signature · 3 lines
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
Reviewed-by on v1 1/1
#2 lore raw
In reply to Thomas Huth
Quoted 8 lines · Thomas Huth

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.

Quoted 8 lines

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.

---
  .gitlab-ci.d/cirrus.yml | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)