Hi all SIGs!
As we all switched (for SIGs) to gitlab.com in the last months (and final archive was done for all /rpms/* and other projects still on pagure/git.centos.org) some SIGs started to explore other gitlab features, like CI/CD.
We got this week a warning from Gitlab about our CentOS project almost reaching the allocated quota in our sponsored account there, but it should be reset on monthly basis and it shouldn't be blocking any of your CI/CD pipelines for this week.
But we still need to verify about which SIGs are (ab)using the "compute minutes" allocated for our account and find a better/optimized way to let you still use CI/CD features, but maybe by offloading to some dedicated runners we'd spin up in our own infra . I just created yesterday ticket https://gitlab.com/CentOS/infra/tracker/-/issues/1743 to track this (but need some investigation and time which I had not planned to spent on gitlab for now)
Actually the top 3 projects/groups under CentOS org on gitlab using computes minutes for August are :
- https://gitlab.com/CentOS/automotive/src/automotive-image-builder (~17200 minutes so far) - https://gitlab.com/CentOS/Hyperscale/rpms/systemd (~5400 minutes so far) - https://gitlab.com/CentOS/kmods/rpms/kernel (~1300 minutes so far)
We clearly see an exponential growth for compute minutes usage, but we'd also remind each SIG/project hosted there to be "good citizen" and so think that they are quotas in place that would eventually impact other hosted projects.