Feature/multibranch scan #372
Open
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.
Functionality added to trigger a Jenkins Multibranch pipeline scan when a branch is created or deleted for a Bitbucket repository. Testing completed with Jenkins and Bitbucket Data Center for the scenario of creating a new branch for a Bitbucket repository. After refreshing the Jenkins page for the Multibranch pipeline the new branch appears in the multibranch pipeline. In previous versions a manual scan had to be done before the new branch appeared in the multibranch pipeline even though the webhook request was received from Bitbucket during the addition or deletion events.
Submitter checklist