Re: [GitLab] Group runners: And why CI is slow in forks

Just a short heads up for people following the mail, you can easily set up your own hardware/laptop or cloud as a runner for projects. On the GUADEC's GitLab workshop we did in 5 minutes.

However, what we want is to have a consistent and good experience for CI for the whole GNOME, so that means we need to have them centralized. This is useful to play with it to see costs and how much donation could be made.


On Tue, 24 Jul 2018 at 10:08, Carlos Soriano <csoriano gnome org> wrote:
That sounds great! Seems you know how to set up this which is wonderufl so we can get this going.

Sure, we can make a call, I will follow up off-list.


On Tue, 24 Jul 2018 at 09:15, Walter Vargas <waltervargas linux com> wrote:
Hi Carlos,

Thank you for your concerns regarding the costs associated with CI
infrastructure; the last week I was talking to Emmanuel that I would
like to donate CPU capacity of one of my cloud accounts for the

Please let me know if we can schedule a quick call this week to discuss that.

Additionally, we can create a "Runners Support Program" to allow
people to contribute with runners, that will require:
  1. An automated mechanism to install the required software.
     -  This can be an UserData script or an AMI with all set that we
could publish to the AWS Market.
  2. Support from the Engagement Team to create a social media strategy, etc.

Warm Regards.

On Mon, Jul 23, 2018 at 7:28 AM Carlos Soriano <csoriano gnome org> wrote:
> Hello all,
> In case you missed my treasurer report talk at GUADEC, our annual costs for CI is around $22.000. This is okay since we are lucky to have GitLab Inc. as the main sponsor of that. However, we cannot offload all of our needs on them, even more in the long-term. So we need to 1) find sponsors, 2) make sure we spend money on just GNOME software.
> In order to spend money just in GNOME software we restricted the fast runners to the groups GNOME/ and Infrastructure/. The runners in there are AWS and DO in a elastic set up, that means they get spawned dynamically as the load increases and they are quite beefy. Ideally this would be in a wiki page, with the set up and costs explained.
> However there is an issue, forks and MR of forks are no part of this, so they get the local machine we have instead of the fast runners.
> I was surprised this wasn't mentioned before, but fear not, it's the most upvoted issue upstream right now
> Lately, if you think someone could sponsor part of that money or some machine for the rest of the software not in those groups, please reach to me!
> Cheers
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]