CI: Add scheduled job for container update and regenerate with new lcitool

[PATCH 0/1] CI: Add scheduled job for container update and regenerate with new lcitool

Peter Krempa posted 1 patch 1 year, 2 months ago

Download series mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/cover.1677492153.git.pkrempa@redhat.com

ci/gitlab/build-templates.yml | 2 +-
ci/gitlab/sanity-checks.yml   | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

Expand all Fold all

[PATCH 0/1] CI: Add scheduled job for container update and regenerate with new lcitool

Posted by Peter Krempa 1 year, 2 months ago

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

Re: [PATCH 0/1] CI: Add scheduled job for container update and regenerate with new lcitool

Posted by Daniel P. Berrangé 1 year, 2 months ago

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 :|