You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@grails.apache.org by jd...@apache.org on 2026/08/26 23:53:14 UTC

(grails-core) 01/01: Increaes the queue to max instead of only having 1 that results in job cancels

This is an automated email from the ASF dual-hosted git repository.

jdaugherty pushed a commit to branch doc-publish-fix
in repository https://gitbox.apache.org/repos/asf/grails-core.git

commit b9eb094360ae35a73180e7e3b699c3e5ae2277f9
Author: James Daugherty <jd...@jdresources.net>
AuthorDate: Wed Aug 26 19:52:51 2026 -0400

    Increaes the queue to max instead of only having 1 that results in job cancels
---
 .github/workflows/gradle.yml  | 6 ++++++
 .github/workflows/release.yml | 6 ++++++
 2 files changed, 12 insertions(+)

diff --git a/.github/workflows/gradle.yml b/.github/workflows/gradle.yml
index 28f12cb662..11f03ebee6 100644
--- a/.github/workflows/gradle.yml
+++ b/.github/workflows/gradle.yml
@@ -764,6 +764,12 @@ jobs:
     concurrency:
       group: grails-docs-publish
       cancel-in-progress: false
+      queue: max
+      # `queue: max` is REQUIRED here. `cancel-in-progress: false` only protects the job that
+      # is already running; by default a concurrency group holds just ONE pending job, and a
+      # third entrant CANCELS the pending one rather than lining up behind it. With several
+      # release lines (7.0.x/7.1.x/7.2.x/8.0.x) publishing docs at once, that silently killed
+      # releases. `queue: max` raises the queue to 100 so entrants queue FIFO instead.
     steps:
       - name: "⚙️ Maximize build space"
         run: |
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 951eb3a050..bb1d79c240 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -577,6 +577,12 @@ jobs:
     concurrency:
       group: grails-docs-publish
       cancel-in-progress: false
+      queue: max
+      # `queue: max` is REQUIRED here. `cancel-in-progress: false` only protects the job that
+      # is already running; by default a concurrency group holds just ONE pending job, and a
+      # third entrant CANCELS the pending one rather than lining up behind it. With several
+      # release lines (7.0.x/7.1.x/7.2.x/8.0.x) publishing docs at once, that silently killed
+      # releases. `queue: max` raises the queue to 100 so entrants queue FIFO instead.
     steps:
       - name: "📝 Establish release version"
         run: echo "VERSION=${TAG#v}" >> "$GITHUB_ENV"