Pull Request Building Behaviour
See original GitHub issueYour checklist for this issue
-
Jenkins version - 2.263.1
-
Plugin version - 2.9.5
-
Bitbucket cloud - yes
-
Bitbucket server and version - cloud subscription
Description
We are Using Multibranch Pipelines configured with this plugin. Multibranch pipeline config (relevant part): “Discover pull requests from origin” Enabled with strategy “Merging the pull request with the current target branch revision” “Filter by name with regular expression” behavior enabled with the value “master”
Result: all updates on master branch are received via webhook and trigger a build no PRs get discovered and built
Expected: all updates on master branch are received via webhook and trigger a build all PRs with target branch master are received via webhook and trigger a build
Steps attempted: From some older posts regarding similar issues, there are suggestions ou there to include “PR-.*” on the value of “Filter by name with regular expression” behavior; although this triggers PR builds, all PRs trigger a build with no relation to target branch of the PR
Desired Functionality: Build on every update on master and every PR that has master as a target branch Is this possible within the configuration of this plugin, using bitbucket web?
Additional INFO: webhook setup:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top GitHub Comments
The SCM Filter Branch PR plugin is exactly what you need.
It works nice in combination with the bitbucket branch source plugin as well.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.