[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Serious doubts about Gitlab CI
From: |
Philippe Mathieu-Daudé |
Subject: |
Serious doubts about Gitlab CI |
Date: |
Wed, 17 Mar 2021 21:29:32 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 |
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...
Some screenshots FWIW:
https://pasteboard.co/JT51wGR.png
https://pasteboard.co/JT51Rqq.png
https://pasteboard.co/JT52fNL.png
Regards,
Phil.