On Wed, May 31, 2023 at 04:08:24PM +0100, Camilla Conte wrote: > Previous attempt by Alex Bennée, for the records: > https://lore.kernel.org/qemu-devel/20230330101141.30199-12-alex.ben...@linaro.org/ > > Does not enable caching, as suggested in a previous review: > https://lore.kernel.org/qemu-devel/zcvpmdlpjcdnk...@redhat.com/
In this mail I suggested we entirely skip running kaniko if we determine the dockerfile content is unchanged since last build... > diff --git a/.gitlab-ci.d/container-template.yml > b/.gitlab-ci.d/container-template.yml > index d146d1d197..0e93f5f13e 100644 > --- a/.gitlab-ci.d/container-template.yml > +++ b/.gitlab-ci.d/container-template.yml > + - /kaniko/executor > + --dockerfile "$DOCKERFILE" > + --destination "$TAG" ....this is running kaniko unconditionally on every pipeline. I fear this is going to increase the CI credits we are burning on every pipeline. While QEMU has added its private k8s runner, our contributors forks are still burning limited CI credits. Do you have pipelines showing the CI credit usage of a pipeline before and after this change ? 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 :|
