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
workflows: fix concurrency group names #16711
Merged
Merged
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
nbusseneau
added
area/CI
Continuous Integration testing issue or flake
area/CI-improvement
Topic or proposal to improve the Continuous Integration workflow
release-note/ci
This PR makes changes to the CI.
labels
Jun 30, 2021
nbusseneau
force-pushed
the
pr/fix-workflows-concurrency-for-labels
branch
from
June 30, 2021 14:52
28b1774
to
f73977d
Compare
pchaigno
approved these changes
Jul 1, 2021
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.
LGTM (apart from the one comment below on labels).
I have reviewed carefully the first and only glanced at the others, but I assume they are the same (apart from trigger phrase & label).
nbusseneau
force-pushed
the
pr/fix-workflows-concurrency-for-labels
branch
from
July 1, 2021 15:26
f73977d
to
eac0a76
Compare
Requires #16735. Will unmark as draft once that one is merged. |
nbusseneau
force-pushed
the
pr/fix-workflows-concurrency-for-labels
branch
2 times, most recently
from
July 1, 2021 15:45
01ad081
to
ec42d21
Compare
Improve concurrency group names uniqueness, in particular for allowing testing workflow changes via `pull_request` events. In the previous version, all `pull_request`-triggered runs would end up in the same concurrency group as the `scheduled` events, due to not having a `github.event.issue` object. This new version proposes a new structure that should be unique for all types of testing, while still allowing runs of the same type to override each other: Structure: - Workflow name - Event type - A unique identifier depending on event type: - schedule: SHA - issue_comment: PR number - pull_request: PR number Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
nbusseneau
force-pushed
the
pr/fix-workflows-concurrency-for-labels
branch
from
July 1, 2021 18:00
ec42d21
to
6cca627
Compare
pchaigno
approved these changes
Jul 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/CI
Continuous Integration testing issue or flake
area/CI-improvement
Topic or proposal to improve the Continuous Integration workflow
release-note/ci
This PR makes changes to the CI.
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.
Improve concurrency group names uniqueness, in particular for allowing testing workflow changes via
pull_request
events.In the previous version, all
pull_request
-triggered runs would end up in the same concurrency group as thescheduled
events, due to not having agithub.event.issue
object.This new version proposes a new structure that should be unique for all types of testing, while still allowing runs of the same type to override each other:
Structure: