From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <willianr@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH 0/2] gitlab: prepare for limited CI minutes by not running by default
Date: Thu, 12 Aug 2021 19:04:01 +0100 [thread overview]
Message-ID: <20210812180403.4129067-1-berrange@redhat.com> (raw)
A while ago GitLab announced it would be ending the free unlimited CI
minutes for public projects. It hasn't happened yet, but it is certainly
still on the radar. It is possible for OSS projects to get a greater
allowance, but it is still unclear how this will work for contributors'
forks. Even with the greater allowance, we'll burn through it in just
a few pipeline runs. People creating brand new gitlab accounts are
already getting hurt by the new limits IIUC.
This series isn't a full solution, but it gets us started in a more
sustainable direction. See the second patch commit message and the
docs that it adds for full details.
At a high level though, with this series applied, we no longer run
any CI jobs by default, except for the 'staging' branch in the
'qemu-project' namespace.
Users can manually start any individual job from the web UI still
though. Further, they can opt-in to various sets of jobs
- 100% manual jobs (the new default):
https://gitlab.com/berrange/qemu/-/pipelines/352393697
- A minimal set of jobs
https://gitlab.com/berrange/qemu/-/pipelines/352397093
- A full set of jobs (the old default)
https://gitlab.com/berrange/qemu/-/pipelines/352123582
- A gating set of jobs (identical to what's run on staging)
https://gitlab.com/berrange/qemu/-/pipelines/352195185
With this starting point, the common "rules" definition across
all jobs, makes it easy for us to add more refinements. We can
defining further sets of interesting jobs.
eg could define a set of cross-compilation, or a set for
non-Linux, or a set of Windows, or sets for particular host
architectures, etc.
Daniel P. Berrangé (2):
docs: split the CI docs into two files
gitlab: don't run CI jobs by default on push to user forks
.gitlab-ci.d/buildtest-template.yml | 17 +--
.gitlab-ci.d/buildtest.yml | 43 +++----
.gitlab-ci.d/cirrus.yml | 6 +-
.gitlab-ci.d/container-core.yml | 4 +
.gitlab-ci.d/container-cross.yml | 9 +-
.gitlab-ci.d/container-template.yml | 1 +
.gitlab-ci.d/containers.yml | 4 +
.gitlab-ci.d/crossbuild-template.yml | 3 +
.gitlab-ci.d/crossbuilds.yml | 3 +
.gitlab-ci.d/qemu-project.yml | 1 +
.gitlab-ci.d/rules.yml | 116 +++++++++++++++++++
.gitlab-ci.d/static_checks.yml | 18 +--
.gitlab-ci.yml | 4 -
docs/devel/ci-jobs.rst | 161 +++++++++++++++++++++++++++
docs/devel/ci-runners.rst | 117 +++++++++++++++++++
docs/devel/ci.rst | 159 +-------------------------
16 files changed, 459 insertions(+), 207 deletions(-)
create mode 100644 .gitlab-ci.d/rules.yml
create mode 100644 docs/devel/ci-jobs.rst
create mode 100644 docs/devel/ci-runners.rst
--
2.31.1
next reply other threads:[~2021-08-12 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 18:04 Daniel P. Berrangé [this message]
2021-08-12 18:04 ` [PATCH 1/2] docs: split the CI docs into two files Daniel P. Berrangé
2021-08-16 11:02 ` Philippe Mathieu-Daudé
2021-08-24 16:29 ` Willian Rampazzo
2021-08-12 18:04 ` [PATCH 2/2] gitlab: don't run CI jobs by default on push to user forks Daniel P. Berrangé
2021-08-16 10:44 ` Cornelia Huck
2021-08-16 11:03 ` Daniel P. Berrangé
2021-08-16 11:20 ` Philippe Mathieu-Daudé
2021-08-16 11:35 ` Daniel P. Berrangé
2021-08-16 11:45 ` Philippe Mathieu-Daudé
2021-08-16 11:47 ` Cornelia Huck
2021-08-16 12:01 ` Daniel P. Berrangé
2021-08-16 13:19 ` Cornelia Huck
2021-08-16 13:23 ` Daniel P. Berrangé
2021-08-16 15:16 ` Philippe Mathieu-Daudé
2021-08-25 10:42 ` Thomas Huth
2021-09-15 14:45 ` Daniel P. Berrangé
2022-05-10 8:51 ` Thomas Huth
2022-05-10 9:13 ` Daniel P. Berrangé
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=20210812180403.4129067-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).