From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"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 09:33:55 +0000 [thread overview]
Message-ID: <YFMegwL6SXX2/+kZ@redhat.com> (raw)
In-Reply-To: <cb9d0504-aba5-3114-d121-694a5247764c@amsat.org>
On Wed, Mar 17, 2021 at 09:29:32PM +0100, Philippe Mathieu-Daudé wrote:
> Hi,
>
> For some (unclear) reason I got my free tier Gitlab account renewed and
> lost the privilege for users opening account before the quota limit.
>
> I pushed a single branch to my namespace repo to trigger a pipeline.
> 1h later I was surprised to see the pipeline was stuck, having completed
> 99 jobs of 119. Looking closer there is a red comment on top of the
> pipeline:
>
> philmd has exceeded its pipeline minutes quota. Unless you buy
> additional pipeline minutes, no new jobs or pipelines in its projects
> will run. [Buy more Pipelines minutes]
>
> So I exhausted my 400 monthly minutes credit.
>
> From this FAQ:
> https://about.gitlab.com/pricing/faq-consumption-cicd/#managing-your-cicd-minutes-usage
>
> Q. What happens if I hit the CI/CD Minutes allotted limit and forget to
> purchase additional CI/CD Minutes?
>
> A. You will not be able to run new jobs until you purchase additional
> CI/CD Minutes, or until the next month when you receive your monthly
> allotted CI/CD Minutes.
>
> Q. Will I be notified before I hit my limit on CI/CD Minutes?
>
> A. You will receive notification banners in-app when your group has less
> than 30%, 5% or exceeded your total allotted CI/CD minutes.
>
> I indeed received 3 warnings in 7 minutes.
>
> Now I'm having serious doubts about Gitlab usefulness for the QEMU
> community...
Per the discussions in the related Forum postings about CI limites, the
400 minute limit is still only intended to apply to projects that are
marked as private. Public projects are not even being tracked for
accounting, let alone have a limit enforced. They also said they want
to make sure they don't impact ability of users to contribute to OSS
projects hosted on GitLab that require use of CI.
It feels like what you hit here is fallout from your account accidentally
getting blocked, rather than something which is hitting every contributor
to QEMU. Did they restore projects as private perhaps ?
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 :|
next prev parent reply other threads:[~2021-03-18 9:41 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é [this message]
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
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=YFMegwL6SXX2/+kZ@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).