Separate OSS and Standard Cost Factors
Problem
We want to treat CI jobs from the new OSS plan differently than other CI jobs on Free or paid plans. As we plan to harden CI minutes limits for all public projects on Gitlab.com we want to give OSS plan namespaces extra room for CI minutes usage so they are not impacted by the limitations.
Proposal
Separate the cost factor for OSS jobs from the standard cost factor. If project is from OSS plan use 0.008
cost factor. This won't introduce any difference today since the cost factor of new public projects is also 0.008
but as we plan to change it to 1.0
we want to have OSS plan using a lower cost factor.
- if Runner cost factor is
0.0
(old public project), use cost factor as is. - if Runner cost factor is
1.0
(private projects now, in the future any project by default) and project is from OSS plan, lower the cost factor to0.008
. - if Runner cost factor is greater than
1.0
(e.g. macOS runners), use cost factor as is.
Acceptance criteria
- Ensure that this impacts only GitLab ~"SaaS".
- We don't want to raise the cost factor for OSS projects if they are currently using
0.0
as old public projects. - We don't want to lower the cost factor to
0.008
if the project is using special runners which have high cost factor (e.g. macOS runners).
Edited by Fabio Pitino