This is an automated email from the ASF dual-hosted git repository. jacopoc pushed a commit to branch release24.09 in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git
commit f26a1b4727af98b89dd5e8a21c1ffe35fff3eb5f Author: Jacopo Cappellato <[email protected]> AuthorDate: Wed Oct 21 14:36:38 2026 +0200 Give each push build of the Java CI workflow its own concurrency group A concurrency group holds at most one running and one pending run: when a newer run joins the group, the pending one is cancelled even if cancel-in-progress is false. Grouping trunk and release* pushes by github.ref could therefore leave some commits without a build. Use github.run_id for pushes instead, while pull requests are still grouped by number and still have their older runs cancelled. Thanks to Mridul Pathak for the review. Co-Authored-By: Claude Opus 5.5 <[email protected]> (cherry picked from commit 696e14e5b1e289cd5d80026341dc85ba2af3948d) --- .github/workflows/gradle.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/gradle.yml b/.github/workflows/gradle.yml index 6e8f706cbd..f00499b256 100644 --- a/.github/workflows/gradle.yml +++ b/.github/workflows/gradle.yml @@ -58,8 +58,9 @@ on: # A new push to a pull request makes its previous, still running or queued build useless. # Pushes to trunk and release* are never cancelled so that every commit gets its own result. +# Each of them gets its own group (run_id): in a shared group a newer run would replace a pending one. concurrency: - group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }} + group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }} cancel-in-progress: ${{ github.event_name == 'pull_request' }} permissions:
