4:08 a.m.
As it was intended and discussed before I've added a scheduled job named
'Weekly CI container rebuild' which will run the pipeline with
RUN_CONTAINER_BUILDS variable set to 1 to update the containers
regularly rather than doing it manually and very infrequently.
The job will run every Monday at 5AM UTC.
I'll trigger it manually tomorrow if there are no objections.
Note that gitlabs scheduled job permissions are weird so I'm not sure
who will be able to edit or delete the job in the future. I can't do
that for the daily build with coverity.
The patch also regenerates the CI files with latest lcitool
Peter Krempa (1):
ci: Regenerate gitlab config with latest lcitool
ci/gitlab/build-templates.yml | 2 +-
ci/gitlab/sanity-checks.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.39.2
4:08 a.m.
New subject: [PATCH 1/1] ci: Regenerate gitlab config with latest lcitool
The 'cirrus-run' and 'check-dco' containers are now exported as
':latest' instead of ':master'.
Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
---
ci/gitlab/build-templates.yml | 2 +-
ci/gitlab/sanity-checks.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/ci/gitlab/build-templates.yml b/ci/gitlab/build-templates.yml
index 259cf2b173..445bfa63eb 100644
--- a/ci/gitlab/build-templates.yml
+++ b/ci/gitlab/build-templates.yml
@@ -235,7 +235,7 @@
.cirrus_build_job:
stage: builds
- image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
interruptible: true
needs: []
script:
diff --git a/ci/gitlab/sanity-checks.yml b/ci/gitlab/sanity-checks.yml
index cdcfb9bf91..4e33b2dfe3 100644
--- a/ci/gitlab/sanity-checks.yml
+++ b/ci/gitlab/sanity-checks.yml
@@ -8,7 +8,7 @@
check-dco:
stage: sanity_checks
needs: []
- image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:latest
interruptible: true
script:
- /check-dco "$RUN_UPSTREAM_NAMESPACE"
--
2.39.2
4:53 a.m.
New subject: [PATCH 1/1] ci: Regenerate gitlab config with latest lcitool
On Mon, Feb 27, 2023 at 11:08:08AM +0100, Peter Krempa wrote:
The 'cirrus-run' and 'check-dco' containers are now
exported as
':latest' instead of ':master'.
FWIW, I've not deleted the old ':master' tags, so we have time
to update all the various libvirt/libosinfo/virt-viewer/qemu
projects usage.
Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
---
ci/gitlab/build-templates.yml | 2 +-
ci/gitlab/sanity-checks.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/ci/gitlab/build-templates.yml b/ci/gitlab/build-templates.yml
index 259cf2b173..445bfa63eb 100644
--- a/ci/gitlab/build-templates.yml
+++ b/ci/gitlab/build-templates.yml
@@ -235,7 +235,7 @@
.cirrus_build_job:
stage: builds
- image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
interruptible: true
needs: []
script:
diff --git a/ci/gitlab/sanity-checks.yml b/ci/gitlab/sanity-checks.yml
index cdcfb9bf91..4e33b2dfe3 100644
--- a/ci/gitlab/sanity-checks.yml
+++ b/ci/gitlab/sanity-checks.yml
@@ -8,7 +8,7 @@
check-dco:
stage: sanity_checks
needs: []
- image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:master
+ image: registry.gitlab.com/libvirt/libvirt-ci/check-dco:latest
interruptible: true
script:
- /check-dco "$RUN_UPSTREAM_NAMESPACE"
Reviewed-by: Daniel P. Berrangé <berrange(a)redhat.com>
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 :|
4:52 a.m.
On Mon, Feb 27, 2023 at 11:08:07AM +0100, Peter Krempa wrote:
As it was intended and discussed before I've added a scheduled
job named
'Weekly CI container rebuild' which will run the pipeline with
RUN_CONTAINER_BUILDS variable set to 1 to update the containers
regularly rather than doing it manually and very infrequently.
The job will run every Monday at 5AM UTC.
I'll trigger it manually tomorrow if there are no objections.
Sounds good. Trigger now if you like !
Note that gitlabs scheduled job permissions are weird so I'm not
sure
who will be able to edit or delete the job in the future. I can't do
that for the daily build with coverity.
As an admin it won't let me edit, but shows me a "take ownership"
button which should let me edit once pressed. I've not pressed it
to test though.
Feels like a bit of a strange permissions model to me but since
we'll almost never touch these jobs, its not a big deal.
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 :|
633
days inactive
633
days old
3 comments
2 participants
participants (2)
-
Daniel P. Berrangé -
Peter Krempa