Re: [PATCH] .gitlab-ci.d/cirrus.yml: Fix the NetBSD and OpenBSD Cirrus-CI KVM jobs
On 24/4/24 09:42, Thomas Huth wrote: 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 --- .gitlab-ci.d/cirrus.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Philippe Mathieu-Daudé
Re: [PATCH] .gitlab-ci.d/cirrus.yml: Fix the NetBSD and OpenBSD Cirrus-CI KVM jobs
On Wed, Apr 24, 2024 at 09:42:02AM +0200, Thomas Huth wrote: > 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 > --- > .gitlab-ci.d/cirrus.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Daniel P. Berrangé With regards, Daniel -- |: 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 :|
[PATCH] .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. Signed-off-by: Thomas Huth --- .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