From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Serious doubts about Gitlab CI
Date: Thu, 18 Mar 2021 19:46:01 +0000 [thread overview]
Message-ID: <YFOt+R77HfpNEYFc@stefanha-x1.localdomain> (raw)
In-Reply-To: <cb9d0504-aba5-3114-d121-694a5247764c@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On Wed, Mar 17, 2021 at 09:29:32PM +0100, Philippe Mathieu-Daudé wrote:
> Now I'm having serious doubts about Gitlab usefulness for the QEMU
> community...
The QEMU Project has 50,000 minutes of GitLab CI quota. Let's enable
GitLab Merge Requests so that anyone can submit a merge request and get
CI coverage.
I think we need to expect free tiers to be insufficient for full CI
coverage. In the longer term we probably need to rely on dedicated
runners, although I'm not sure how much of the issue is QEMU's huge CI
pipeline versus the performance limitations of shared runners.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-18 19:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:29 Serious doubts about Gitlab CI Philippe Mathieu-Daudé
2021-03-18 1:28 ` Bin Meng
2021-03-18 8:55 ` Philippe Mathieu-Daudé
2021-03-18 9:33 ` Daniel P. Berrangé
2021-03-18 9:50 ` Philippe Mathieu-Daudé
2021-03-18 10:28 ` Philippe Mathieu-Daudé
2021-03-19 5:34 ` Thomas Huth
2021-03-18 19:46 ` Stefan Hajnoczi [this message]
2021-03-18 19:52 ` John Snow
2021-03-18 20:53 ` Philippe Mathieu-Daudé
2021-03-18 20:30 ` Paolo Bonzini
2021-03-19 9:33 ` Stefan Hajnoczi
2021-03-19 9:41 ` Paolo Bonzini
2021-03-19 11:44 ` Philippe Mathieu-Daudé
2021-03-19 10:18 ` Andrew Jones
2021-03-19 10:59 ` Paolo Bonzini
2021-03-19 11:34 ` Philippe Mathieu-Daudé
2021-03-19 15:27 ` Wainer dos Santos Moschetta
2021-03-29 14:10 ` Stefan Hajnoczi
2021-03-30 11:19 ` Daniel P. Berrangé
2021-03-30 11:55 ` Thomas Huth
2021-03-30 12:09 ` Paolo Bonzini
2021-03-30 12:23 ` Philippe Mathieu-Daudé
2021-03-30 12:45 ` Paolo Bonzini
2021-03-30 13:12 ` Daniel P. Berrangé
2021-03-30 13:19 ` Paolo Bonzini
2021-03-30 13:27 ` Daniel P. Berrangé
2021-03-30 15:59 ` Warner Losh
2021-03-30 16:11 ` Peter Maydell
2021-03-30 16:24 ` Warner Losh
2021-03-30 16:10 ` Thomas Huth
2021-03-30 13:09 ` Daniel P. Berrangé
2021-03-30 12:09 ` Paolo Bonzini
2021-03-30 12:19 ` Peter Maydell
2021-03-30 12:33 ` Philippe Mathieu-Daudé
2021-03-30 13:19 ` Daniel P. Berrangé
2021-03-31 7:54 ` Thomas Huth
2021-03-31 9:31 ` Andrea Bolognani
2021-03-30 14:13 ` Stefan Hajnoczi
2021-03-30 14:23 ` Paolo Bonzini
2021-03-30 14:30 ` Daniel P. Berrangé
2021-03-30 14:09 ` Stefan Hajnoczi
2021-03-19 12:07 ` Markus Armbruster
2021-03-19 13:06 ` Thomas Huth
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=YFOt+R77HfpNEYFc@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).