Skip to content

Use concurrency groups in CI to prevent overfilling the queue#3794

Merged
thomas-bc merged 4 commits intonasa:develfrom
thomas-bc:ci/concurrency
Jun 24, 2025
Merged

Use concurrency groups in CI to prevent overfilling the queue#3794
thomas-bc merged 4 commits intonasa:develfrom
thomas-bc:ci/concurrency

Conversation

@thomas-bc
Copy link
Collaborator

Related Issue(s)
Has Unit Tests (y/n)
Documentation Included (y/n)

Change Description

Fix #3793

This should help with not overloading the CI queue too much, by cancelling previous runs if a newer commit has been pushed to a PR branch. The cancelling does not apply to devel or release/ branches.

@thomas-bc thomas-bc changed the title Ci/concurrency Use concurrency groups in CI to prevent overfilling the queue Jun 24, 2025
@thomas-bc
Copy link
Collaborator Author

Shown in the commit above - all runs on the Rephrase 20dc12b commit have been cancelled once the merge commit was pushed.

image

Copy link
Collaborator

@LeStarch LeStarch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not cancel devel jobs too? Not a blocker.

@thomas-bc
Copy link
Collaborator Author

This is simply to get successful checks on every commit on devel. History would "appear" questionable if we start getting lots of failure-looking checks simply because they're cancelled. I agree it'd be more efficient to cancel on devel as well... but I kind of like the sea of green checkmarks on devel haha

@thomas-bc thomas-bc merged commit 6bdeb5a into nasa:devel Jun 24, 2025
50 checks passed
@thomas-bc thomas-bc deleted the ci/concurrency branch June 24, 2025 19:36
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.

Use concurrency groups in CI

2 participants