From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/5] gitlab: restrict running jobs in forks and upstream master
Date: Thu, 26 May 2022 07:07:00 -0400 [thread overview]
Message-ID: <20220526110705.59952-1-berrange@redhat.com> (raw)
Currently on upstream most jobs will run in both staging
and master. This is quite wasteful of CI credits. The only
need to run in master is for the jobs related to publishing
the website
In forks we run jobs on every push. With restricted CI
allowance this is quickly going to cause problems.
With this series jobs will no longer run on forks at all,
without an opt-in with QEMU_CI=1 (pipeline with manual
jobs) or QEMU_CI=2 (pipeline with immediate jobs)
This is a rewrite of a previous proposal:
https://lists.nongnu.org/archive/html/qemu-devel/2021-08/msg02104.html
where I've kept it simpler and also split up the patches
into more understandable chunks
Daniel P. Berrangé (5):
gitlab: introduce a common base job template
gitlab: convert Cirrus jobs to .base_job_template
gitlab: convert static checks to .base_job_template
gitlab: convert build/container jobs to .base_job_template
gitlab: don't run CI jobs in forks by default
.gitlab-ci.d/base.yml | 72 +++++++++++++++++++++++
.gitlab-ci.d/buildtest-template.yml | 16 ++---
.gitlab-ci.d/buildtest.yml | 28 ++++-----
.gitlab-ci.d/cirrus.yml | 16 ++---
.gitlab-ci.d/container-cross.yml | 6 +-
.gitlab-ci.d/container-template.yml | 1 +
.gitlab-ci.d/crossbuild-template.yml | 3 +
.gitlab-ci.d/qemu-project.yml | 1 +
.gitlab-ci.d/static_checks.yml | 19 +++---
.gitlab-ci.d/windows.yml | 1 +
docs/devel/ci-jobs.rst.inc | 88 +++++++++++++++++++++++++++-
11 files changed, 199 insertions(+), 52 deletions(-)
create mode 100644 .gitlab-ci.d/base.yml
--
2.36.1
next reply other threads:[~2022-05-26 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 11:07 Daniel P. Berrangé [this message]
2022-05-26 11:07 ` [PATCH 1/5] gitlab: introduce a common base job template Daniel P. Berrangé
2022-05-26 11:07 ` [PATCH 2/5] gitlab: convert Cirrus jobs to .base_job_template Daniel P. Berrangé
2022-05-26 11:07 ` [PATCH 3/5] gitlab: convert static checks " Daniel P. Berrangé
2022-05-26 11:07 ` [PATCH 4/5] gitlab: convert build/container jobs " Daniel P. Berrangé
2022-06-02 17:41 ` Thomas Huth
2022-06-06 10:50 ` Daniel P. Berrangé
2022-05-26 11:07 ` [PATCH 5/5] gitlab: don't run CI jobs in forks by default Daniel P. Berrangé
2022-05-26 15:34 ` Marc-André Lureau
2022-05-26 17:08 ` Alex Bennée
2022-05-27 13:27 ` [PATCH 0/5] gitlab: restrict running jobs in forks and upstream master Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220526110705.59952-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.