You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newer versions of BitBucket server send a push event that indicates branch deletion. Currently, we don't gracefully handle this because the scan logic is attempted. If it is a branch name meeting the protected branch name criteria, it fails to scan because the branch is deleted.
This means we also don't handle the project deletion the same way as other SCMs.
Proposed solution
Implement the same logic as in GitHub to not scan delete push events and to delete SAST projects for the branch.
Additional details
This is an example payload from BB server 7.10.0. Note the "changes" section.
Describe the problem
Newer versions of BitBucket server send a push event that indicates branch deletion. Currently, we don't gracefully handle this because the scan logic is attempted. If it is a branch name meeting the protected branch name criteria, it fails to scan because the branch is deleted.
This means we also don't handle the project deletion the same way as other SCMs.
Proposed solution
Implement the same logic as in GitHub to not scan delete push events and to delete SAST projects for the branch.
Additional details
This is an example payload from BB server 7.10.0. Note the "changes" section.
The text was updated successfully, but these errors were encountered: