Hi Bob, Thanks for the heads-up, and for the pointers to the reporting tool and the recommended-practices page.
We've already taken a first concrete step: PR apache/celeborn#3729[1] adds a concurrency group with cancel-in-progress to all of our PR-triggered workflows (Maven, SBT, integration, C++ integration, and Grafana). It's now merged to main, so outdated runs are automatically cancelled when a PR is pushed again, which should noticeably cut our concurrent-job count. We're continuing to look at streamlining the longer builds. The main items on our list: - Trimming/optimising the Java × Spark × Flink test matrices so we cover the important combinations without running everything on every change. - Adding paths/paths-ignore filters so docs- and non-code changes don't trigger the full build suite. - Improving build caching to shorten individual job durations. We'll keep an eye on our usage via the infra reporting tool, join the project-workflow-optimisations Slack channel, and share anything reusable back on the cwiki page. Thanks again, Jiashu Xiong, on behalf of the Apache Celeborn community [1] https://github.com/apache/celeborn/pull/3729 Robert Thomson <[email protected]> 于2026年6月12日周五 20:50写道： > Hi, > > In 2024, the ASF introduced the policy for GitHub Actions usage across > the foundation[1]. As you have likely experienced, the ASF Github > shared pool of Github-hosted runners has been at, or very close to the > limit of 900 jobs most of the time in the past few weeks, causing jobs > to queue for lengthy periods before running. > > Your project has been identified as being among the top consumers of > build time over the past 7 days and 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 >
