Limit CI concurrency to one per PR, redux #261
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ray-Eldath
force-pushed
the
revert-258-revert-233-ci-concurrency
branch
from
e3e1625
to
0881a53
Compare
Ray-Eldath
changed the title
Ray-Eldath
force-pushed
the
revert-258-revert-233-ci-concurrency
branch
from
0881a53
to
a3884f3
Compare
This reverts commit 6fa22ec. Revert "Revert "Limit CI concurrency to one per PR"" In current workflow, when newer commit comes, old pipeline won't get canceled, which wastes resources and cause unnecessary CI failure emails. This PR limits concurrency to one per PR. when newer commit comes, stale CI jobs will be automatically cancelled. See: https://stackoverflow.com/a/72408109/8711684 See: cloudberrydb#258
my-ship-it
force-pushed
the
revert-258-revert-233-ci-concurrency
branch
from
a3884f3
to
5190f9d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should only be merged after CI pipeline considered stable again.
This PR reverts #258.
In current workflow, when newer commit comes, old pipeline won't get canceled, which wastes resources and cause unnecessary CI failure emails. This PR limits concurrency to one per PR. when newer commit comes, stale CI jobs will be automatically cancelled.
See: https://stackoverflow.com/a/72408109/8711684