Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit CI concurrency to one per PR #233

Merged
merged 1 commit into from
Oct 23, 2023

Conversation

Ray-Eldath
Copy link
Contributor

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

@Ray-Eldath
Copy link
Contributor Author

I've tested in #206 that this approach takes effect. stale jobs get cancelled automatically.

image

@avamingli
Copy link
Contributor

Sounds good.

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
Copy link
Contributor

@baotingfang baotingfang left a comment

Choose a reason for hiding this comment

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

LGTM

@Ray-Eldath
Copy link
Contributor Author

how about merge this to make our ci pipeline more efficient? :-) @my-ship-it

@my-ship-it my-ship-it merged commit 3bb6d7d into apache:main Oct 23, 2023
5 checks passed
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.

4 participants