Skip to content

Add concurrency groups to all PR-triggered workflows (branch_9x)#4319

Merged
janhoy merged 2 commits intoapache:branch_9xfrom
janhoy:add-concurrency-to-workflows-9x
Apr 23, 2026
Merged

Add concurrency groups to all PR-triggered workflows (branch_9x)#4319
janhoy merged 2 commits intoapache:branch_9xfrom
janhoy:add-concurrency-to-workflows-9x

Conversation

@janhoy
Copy link
Copy Markdown
Contributor

@janhoy janhoy commented Apr 22, 2026

This does the same for branch_9x that #4318 does for main.

Changes

Add a concurrency block to all 7 GitHub Actions workflows that are triggered by pull_request:

  • bin-solr-test.yml
  • docker-test.yml
  • gradle-extraction-check.yml
  • gradle-precommit.yml
  • solrj-test.yml
  • tests-via-crave.yml
  • validate-changelog.yml

Add cancel-in-progress concurrency blocks to all 7 GitHub Actions
workflows triggered by pull_request. This ensures that when a new
commit is pushed to a PR, any already-queued or in-progress runs for
that PR are cancelled, avoiding wasted resources and reducing queue
delays for new commits.
@janhoy janhoy requested a review from dsmiley April 22, 2026 10:41
Replace the run-scoped workspace path (GITHUB_RUN_ID_GITHUB_RUN_NUMBER)
with a PR-scoped path (prs/<pr-number>) via a CRAVE_WORKSPACE env var.

When cancel-in-progress cancels a run, the cleanup step may not finish,
leaving a stale workspace. With a PR-scoped path, the next run's
"Destroy previous clone" step will always clean up any leftover resources
from a prior run for the same PR, regardless of how it ended.

Backport of apache#4318.
@janhoy janhoy merged commit 4c9a0e3 into apache:branch_9x Apr 23, 2026
6 of 8 checks passed
@janhoy janhoy deleted the add-concurrency-to-workflows-9x branch April 23, 2026 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant