-
Notifications
You must be signed in to change notification settings - Fork 7
[CI] Do not cancel concurrent CI jobs on main #221
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
Conversation
3be3a90
to
e0b8659
Compare
When we merge a PR into the main branch before the previously merged commit finishes, the CI jobs will be cancelled, which is not ideal as we would like to see if all commits merged into main can pass CI checks.
e0b8659
to
f0413c6
Compare
Hey team, Could we have this reviewed and merged when time permits :) This will reduce the CI failed email bombing when we merge dependabot PRs in quick succession! Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree! Jobs shouldn't be canceled on the main branch. Thanks for implementing it.
This is somehow not working on main branch. I will fix this in a follow-up PR... |
Our docker images being pushed to the GitHub registry relies on the CI runs against the main branch, so we need to ensure that the CI runs on main branch is always running without any hiccups. For some reason, #221 fails to address the cancellation on CI runs against main branch. Thus, in this PR, a change is introuduced to revert #160.
For some reason, #221 fails to address the cancellation on CI runs against main branch. Our docker images being pushed to the GitHub registry relies on the CI runs against the main branch, so we need to ensure that the CI runs on main branch is always running without any hiccups.
When we merge a PR into the main branch before the previously merged commit finishes, the CI jobs will be cancelled (see https://github.com/netbox-community/netbox-operator/commits/main/), which is not ideal as we would like to see if all commits merged into the main branch can pass CI checks.