Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Duplicate
-
None
Description
Problem
Branch indexing aborts when one of the branches or pull requests has an unexpected problem, e.g. when a pull request refers to a deleted branch.
Proposed solutions
- Well-known situations (like the one mentioned above) should be handled gracefully and the corresponding branch jobs should be deleted automatically.
- For unexpected errors, only the current branch should be skipped. Branch indexing should continue with the next branch.
Attachments
Issue Links
- duplicates
-
JENKINS-43507 Allow SCMSource and SCMNavigator subtypes to share common traits
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Link |
This issue duplicates |
Resolution | Duplicate [ 3 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
The problem arises when a PR refers to a deleted branch where the source commit no longer exists. I cannot currently reconstruct how this situation came about in our Bitbucket repo, but this plugin should be able to cope with such situations.
The point is that `BitbucketCloudApiClient.resolveSourceFullHash()` does not handle API errors, resulting in `BitbucketRequestException`.
I'll submit a pull request which I've tested with a local build of the plugin.