Skip to contentSkip to conversation

gitlab-ci: Fix the cirrus pipelines

PATCH In review Thomas Huth 2 participants 3 messages Apr 15, 2024 KVM

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gitlab-ci: Fix the cirrus pipelines

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

---
 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
.gitlab-ci.yml +1 -1
index ff34b1f5..98177cdb 100644
@@ -308,7 +308,7 @@ build-centos7:
 #   https://gitlab.com/libvirt/libvirt/-/blob/v7.0.0/ci/README.rst
 #
 .cirrus_build_job_template: &cirrus_build_job_definition
- image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
  before_script:
   - sed -e "s|[@]CI_REPOSITORY_URL@|$CI_REPOSITORY_URL|g"
         -e "s|[@]CI_COMMIT_REF_NAME@|$CI_COMMIT_REF_NAME|g"
Signature · 1 line
2.44.0
Reviewed-by on v1 1/1
#1 lore raw
Quoted 2 lines · Thomas Huth

Pulling the "master" libvirt-ci containers does not work anymore, so we have to switch to the "latest" instead. See also:

We explicitly changed to publish under the 'latest' tag.

Quoted 1 line

https://gitlab.com/libvirt/libvirt/-/commit/5d591421220c850aa64a640

This commit is the root cause:

https://gitlab.com/libvirt/libvirt-ci/-/commit/6e3c5ccac77714be70c0dc52c5210c7cda8fe40f

The effects were dormant for a year as I didn't delete the old ':master' tags until two weeks ago.

Quoted 1 line
Quoted 20 lines
---
 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
.gitlab-ci.yml +1 -1
index ff34b1f5..98177cdb 100644
@@ -308,7 +308,7 @@ build-centos7:
 #   https://gitlab.com/libvirt/libvirt/-/blob/v7.0.0/ci/README.rst
 #
 .cirrus_build_job_template: &cirrus_build_job_definition
- image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
  before_script:
   - sed -e "s|[@]CI_REPOSITORY_URL@|$CI_REPOSITORY_URL|g"
         -e "s|[@]CI_COMMIT_REF_NAME@|$CI_COMMIT_REF_NAME|g"
Signature · 1 line
2.44.0

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 :|
#2 lore raw
Quoted 6 lines · Daniel P. Berrangé
Quoted 2 lines · Thomas Huth

Pulling the "master" libvirt-ci containers does not work anymore, so we have to switch to the "latest" instead. See also:

We explicitly changed to publish under the 'latest' tag.

Quoted 8 lines
Quoted 1 line

https://gitlab.com/libvirt/libvirt/-/commit/5d591421220c850aa64a640

This commit is the root cause:

   https://gitlab.com/libvirt/libvirt-ci/-/commit/6e3c5ccac77714be70c0dc52c5210c7cda8fe40f

The effects were dormant for a year as I didn't delete the old ':master' tags until two weeks ago.

Thanks! I added that information to the commit message and pushed the patch to the repository.

Thomas