On Fri, Sep 04, 2020 at 05:08:36PM +0100, Daniel P. Berrangé wrote: > On Fri, Sep 04, 2020 at 04:35:34PM +0100, Alex Bennée wrote: > > > > Hi, > > > > Given our growing reliance on GitLab and the recent announcement about > > free tier minutes: > > > > https://about.gitlab.com/pricing/faq-consumption-cicd/ > > > > is it time we officially apply for GitLab's Open Source Program: > > > > https://about.gitlab.com/solutions/open-source/program/ > > > > ? > > > > From what I can see the QEMU project will easily qualify - the only > > minor inconvenience is needing to reapply every year. So far it seems as > > a public project their are no usage limits anyway. We are currently > > listed as 0 of 50,000 minutes: > > > > https://gitlab.com/groups/qemu-project/-/usage_quotas#pipelines-quota-tab > > I suspect that ultimately we will end up wanting / needing to do > this. As you say, there's no significant downside, and it will > unlock features. > > Note there is an issue open about making the application process > simpler: > > https://gitlab.com/groups/gitlab-com/marketing/community-relations/opensource-program/-/epics/18 > > which could be a reason to not rush into applying immediately > if we don't have an obvious pressing need. > > As you say there's no enforcement of CI minutes at all right now > anyway as reported at: > > https://gitlab.com/gitlab-org/gitlab/-/issues/243722
FYI, I've very roughly summed up the CI minutes consumed on https://gitlab.com/qemu-project/qemu/-/pipelines/192481227/builds and it comes to around 1400 minutes. So the default 400 minute limit proposed is clearly useless. The Open Source Program offers 50,000 minutes. With our current set of jobs that allows for 35 CI pipelines per month, barely one per day. IOW, I fear QEMU will easily hit the GitLab CI minute quota even with the 50k minutes per month limit. Libvirt only uses about 450 CI minutes per pipeline, but we merge code on a more frequent basis since we don't use the pull request model, so we'll use up a 50k minutes allowance very quickly too. It looks like joining the Open Source program is a must have as the proposde 400 CI minute quota is unusably small. Even once we do that though, it looks inescapable that projects of our scale will need to bring more of our own CI hardware to the table, or failing that, continue to leverage a wide variety 3rd party CI systems (travis, cirrus, etc). It is still unclear how we'll cope with contributors doing CI in their own forks, but GitLab continue to offer positive feedback that they want to make projects in our situation succesful and thus want to find some kind of solution to the CI quota problem with the forking workflow. 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 :|