2:56 p.m.
Before anyone adds any more github actions to projects in the 'wildfly'
github org, please discuss here or in zulip.
GH actions jobs have been essentially free for a long time from our naive
POV, but we do have a max of 20 concurrent jobs across the whole github
org, which we're starting to hit
So we should discuss new ones to make sure they are a good use of our limit.
Best regards,
Brian
8:42 a.m.
Just out of curiosity, I can't find this in the documentation. What happens
if you hit more than 20 concurrent jobs? They are just not started/listed,
do they wait for when they could run within 20 concurrent jobs, or maybe
they are rejected/canceled and GH doesn't track the restart?
Cheers,
Martin Stefanko
Principal Software Engineer
Middleware Runtimes Sustaining Engineering Team
Red Hat
On Thu, Oct 12, 2023 at 9:58 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
Before anyone adds any more github actions to projects in the
'wildfly'
github org, please discuss here or in zulip.
GH actions jobs have been essentially free for a long time from our naive
POV, but we do have a max of 20 concurrent jobs across the whole github
org, which we're starting to hit
So we should discuss new ones to make sure they are a good use of our
limit.
Best regards,
Brian
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
9 a.m.
AFAICT they wait for an open runner. That is the behavior we were observing
last week.
I don't know if there are any queue time or queue length limits around
that. I expect if there are they wouldn't really be relevant to our normal
use; e.g. they'd be GitHub protecting itself against user errors or malice.
On Tue, Oct 17, 2023 at 8:43 AM Martin Stefanko <mstefank(a)redhat.com> wrote:
Just out of curiosity, I can't find this in the documentation.
What
happens if you hit more than 20 concurrent jobs? They are just not
started/listed, do they wait for when they could run within 20 concurrent
jobs, or maybe they are rejected/canceled and GH doesn't track the restart?
Cheers,
Martin Stefanko
Principal Software Engineer
Middleware Runtimes Sustaining Engineering Team
Red Hat
On Thu, Oct 12, 2023 at 9:58 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
> Before anyone adds any more github actions to projects in the 'wildfly'
> github org, please discuss here or in zulip.
>
> GH actions jobs have been essentially free for a long time from our naive
> POV, but we do have a max of 20 concurrent jobs across the whole github
> org, which we're starting to hit
>
> So we should discuss new ones to make sure they are a good use of our
> limit.
> Best regards,
> Brian
>
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> List Archives:
>
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
10:37 a.m.
Late reply, not sure how I missed this :)
On Tue, Oct 17, 2023 at 6:43 AM Martin Stefanko <mstefank(a)redhat.com> wrote:
Just out of curiosity, I can't find this in the documentation.
What
happens if you hit more than 20 concurrent jobs? They are just not
started/listed, do they wait for when they could run within 20 concurrent
jobs, or maybe they are rejected/canceled and GH doesn't track the restart?
The limits are documented here
https://docs.github.com/en/actions/learn-github-actions/usage-limits-bill....
For the free plan you get 20 runners. And yes, what happens is jobs just
stack up and wait for runners to become available.
The biggest issues is that runners are shared across the organization, so
that's 20 runners for everything under https://github.com/wildfly. I've
filed https://github.com/wildfly/wildfly/pull/17300 to help reduce the
number of jobs for WildFly itself.
Cheers,
Martin Stefanko
Principal Software Engineer
Middleware Runtimes Sustaining Engineering Team
Red Hat
On Thu, Oct 12, 2023 at 9:58 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
> Before anyone adds any more github actions to projects in the 'wildfly'
> github org, please discuss here or in zulip.
>
> GH actions jobs have been essentially free for a long time from our naive
> POV, but we do have a max of 20 concurrent jobs across the whole github
> org, which we're starting to hit
>
> So we should discuss new ones to make sure they are a good use of our
> limit.
> Best regards,
> Brian
>
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> List Archives:
>
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
>
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
--
James R. Perkins
JBoss by Red Hat
395
days inactive
406
days old
3 comments
3 participants
participants (3)
-
Brian Stansberry -
James Perkins -
Martin Stefanko