Status: Resolved (View Workflow)
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.
- 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.
JENKINS-43507 Allow SCMSource and SCMNavigator subtypes to share common traits
Harald Wellmann added a comment -
Harald Wellmann added a comment - PR: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/30
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.