Fix BB ambiguous commit status key #4544
Merged
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.
Description
Bitbucket commit status depends on the status key (key=id). A status with the same key overwrites the previous status, even when the triggering event is different (e.g., pull_request or branch).
Problem
When
pull_request
andpush
events are enabled, the commit status is overwritten by the last workflow to finish (only when there's a PR open). This happens because both workflow keys are equal.Solution
Set the key depending on the pipeline context, like the BB data center. Users can use BB settings to block their PRs depending on the workflow name.