Hi Bob,

Thanks for the notification !

There was a spike in runners because we are preparing a release and over 50
contributions required verification to ensure our software quality
This kind of spikes should happen every 3 months unless there is a special
case and due to the amount of patches can not be avoided

Best regards
Alin J

On Mon, Aug 3, 2026 at 8:09 PM Robert Thomson <[email protected]> wrote:

> Hi,
>
> In 2024, the ASF introduced the policy for GitHub Actions usage across
> the foundation[1]. As you have likely experienced, the ASF's Github
> shared pool of Github-hosted runners has been at the maximum limit of
> the number of jobs that can run most of today, causing all project's
> jobs to queue for lengthy periods before running, and your project has
> been identified as using 100 hours of GitHub Actions runner time every
> hour today. We request that you make efforts to bring your usage down
> by stream-lining long-running builds and minimising the number of
> concurrent builds.
>
> You can use the infra reporting tool [2] to monitor your GHA usage as you
> work on stream-lining and to locate any bottlenecks in the workflows.
>
> There is now on-going community discussion on a Slack channel,
> “project-workflow-optimisations” about the topic of optimising GitHub
> Actions workflows so as to minimise both the number of concurrent jobs
> running on our limited allocation, and the number of long-running
> jobs.
>
> To share best practices between projects on this area we encourage
> projects to contribute to this cwiki page:
>
>
> https://cwiki.apache.org/confluence/display/INFRA/GitHub+Actions+Recommended+Practices
>
> It is also possible for a project to maintain their own self-hosted
> runners if they can provide a suitable VM/on-prem hardware to execute
> the runner:
>
>
> https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners
>
> Kind regards,
> Bob Thomson, on behalf of ASF Infrastructure.
>
>
> [1] https://infra.apache.org/github-actions-policy.html
> [2] https://infra-reports.apache.org/#ghactions
>

Reply via email to