Use CANCELLED build state in Bitbucket Data Center and Server 8.0 (#606) #906
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.
Adds an option to the Status Notification Trait to guide what notification to send to Bitbucket when the Jenkins build result is ABORTED.
This PR restores the default behavior for the NOT_BUILT notification from SUCCESS to FAILED (configurable to STOPPED) for Bitbucket Cloud; the SUCCESS state was incorrectly introduced in 2022 as the default instead of STOPPED when the disableNotificationForNotBuildJob configuration option was added (the name can be misinterpreted).
Adds missing guidance description for each configurable option in the Build Status Notification Trait.
Status Notification Summary
The STOPPED status prevents merge checks on Cloud
CANCELLED status should prevents merge checks on Data Center