From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] gitlab: don't run CI jobs by default on push to user forks
Date: Tue, 10 May 2022 10:13:34 +0100 [thread overview]
Message-ID: <YnosvmVvY8mT5Ijp@redhat.com> (raw)
In-Reply-To: <89103e61-3ff0-c374-2317-585ebfb93e6f@redhat.com>
On Tue, May 10, 2022 at 10:51:09AM +0200, Thomas Huth wrote:
> On 12/08/2021 20.04, Daniel P. Berrangé wrote:
> > Currently pushes to user forks run the same set of build / test jobs as
> > pushes to the main repo. This results in creation of 120+ individual
> > jobs. While it is useful for subsystem maintainers, and even regular
> > contributors to be able to run the full set of jobs, it is wasteful to
> > run all of them all the time.
>
> Hi Daniel!
>
> Now that gitlab introduces limits for the CI for all users, I think we
> should revisit this topic ... could you maybe respin your patch to the
> current git master branch?
Yes, I really do need to revisit this patch.
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 :|
prev parent reply other threads:[~2022-05-10 9:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 18:04 [PATCH 0/2] gitlab: prepare for limited CI minutes by not running by default Daniel P. Berrangé
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é [this message]
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=YnosvmVvY8mT5Ijp@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 \
/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).