Re: [eclipse.org-committers] GitHub Actions CI Jobs

[Adam Gibson <adam@xxxxxxxxxx>]

Hi Marc,

I'm the lead for the eclipse deeplearning4j project.

I'm wondering if our builds might have been the cause of that.

I wasn't aware of any quota limits I could find, but our builds just run every 12 hours now and publish snapshots.

Early March we were doing quite a bit, but I've also added safeguards in the builds to prevent more than 1 of the same kind of build from running

as well as auto cancellation of stale jobs as well.

If there's anything else I might be able to help with here, let me know. I'd also be happy to be aware of what other projects are doing to ensure we can split the resources evenly.

Best,

Adam

On Tue, Mar 23, 2021 at 9:54 PM Marc Nuri <marc@xxxxxxxxxxxx> wrote:

Hi Everyone,

I'm Marc, a project lead for Eclipse JKube [1].

For the last couple of days, the number of jobs that run concurrently for our GH action workflows have decreased drastically. Workflows which typically complete in < 20 minutes now take several hours (close to a day).

This happened too early in March after a few GH incidents which made some of our jobs remain stale for 36 hours (default timeout) consuming the concurrency quota. So given the previous experience, yesterday I opened a support ticket (#1074510) to see if we were being affected by the same issue.

I received a reply a few hours later indicating that the problem is that we are hitting concurrency limits at an organization level. I checked a few other Eclipse repositories and saw that other repositories were facing the same issue. Maybe this is related to the sunsetting of build.eclipse.org [3]?

I can't find any entries in the wiki [4] related to this topic, so here are a few open questions:

Are there any plans to increase the GH action resource quota? should we look at some other alternatives and migrate our jobs? is it possible that Eclipse self-hosts GH action runners [5] maybe using the same Azure resources used elsewhere?

Personally, since our project is hosted on GitHub, I like the use of GH actions because they integrate really well into our current contributor + PR workflow. Everything remains open and it's really simple to manage.

Cheers

[1] https://github.com/eclipse/jkube/

[2] https://support.github.com/ticket/personal/0/1074510

[3] https://www.eclipse.org/lists/eclipse.org-committers/msg01248.html

[4] https://wiki.eclipse.org/CBI

[5] https://docs.github.com/en/actions/hosting-your-own-runners

-- 
Marc

_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-committers