CI Minute Quotas for Public Projects of New Namespaces to increase visibility into pipeline minute spend
Release notes
If you wanted to get a complete picture of your CI minute consumption it would be really challenging because public projects are excluded from quotas. With this release, we are including public projects for CI pipeline minute quotas. For a namespace on a free plan, they will have 50,000 minutes for their jobs to run in public projects. Check out our documentation on CI pipeline minute quotas for more information.
Problem to solve
Public projects have a different CI minutes limit and quota than private projects. This issue will document the change and track all communication changes.
Proposal
| Plan | CI minutes limit | Min duration (using private projects only / cost factor 1.0) | Max duration (using public projects only / cost factor 0.008) |
|---|---|---|---|
| Free | 400 | 400 | 50,000 |
| Premium | 10,000 | 10,000 | 1,250,000 |
| Ultimate | 50,000 | 50,000 | 6,250,000 |
This means that for a namespace on Free plan we still show that the limit is 400 but it could run jobs for 400 to 50,000 minutes depending on the combination of private/public projects.
Next steps
-
Create documentation - https://docs.gitlab.com/ee/subscriptions/gitlab_com/index.html#ci-pipeline-minutes -
Create release post - gitlab-com/www-gitlab-com!86008 (merged) -
Let tech evangelism know of change -
Update existing blog post - https://about.gitlab.com/blog/2021/05/17/prevent-crypto-mining-abuse/
Related Links
- Feedback Issue: #336306 (closed)
- Allow historical view of CI Minutes - #246844 (closed)