-
Bug
-
Resolution: Fixed
-
Blocker
-
None
If scanning / indexing fails, we should not apply the orphaned item strategy otherwise we can end up deleting things that were missed from indexing just because an API rate limit has been hit
- relates to
-
JENKINS-36029 multibranch-job deleted when bitbucket communication fails
-
- Closed
-
OK I think this is not a bug... at least with Branch API 2.0.0+ and implementations of SCMNavigator that assign consistent IDs to their SCMSource instances.
With older versions of Branch API it may have occurred but the new code path seems fine