On Thu, Oct 06, 2022 at 10:52:03AM +0200, Peter Krempa wrote:
On Thu, Oct 06, 2022 at 09:20:08 +0100, Daniel P. Berrangé wrote:
On Thu, Oct 06, 2022 at 09:42:26AM +0200, Peter Krempa wrote:
On Tue, Oct 04, 2022 at 08:51:50 -0400, Daniel P. Berrangé wrote:
This refresh switches the CI for contributors to be triggered by merge requests. Pushing to a branch in a fork will no longer run CI pipelines, in order to avoid consuming CI minutes. To regain the original behaviour contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This should be also documented in ci/README.rst as this commit message will become gradually harder to find.
It is present in comments at the top of ci/gitlab.yml, along with info about some other variables that exist.
Ah, okay. So in that case, ci/README.rst should point out that the yml file has further docs, so that the users don't have to look too deep.
I'll add this to ci/README.rst when pushing: +GitLab CI tuning +================ + +The behaviour of GitLab CI can be tuned through a number of variables +which can be set at push time, or through the UI. See ``ci/gitlab.yml`` +for further details. 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 :|