-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: bitbucket-branch-source-plugin
-
Labels:None
-
Environment:Jenkins 1.642
bitbucket-branch-source-plugin 1.5
scm-api 1.2
-
Similar Issues:
When a multibranch pipeline is created with Bitbucket, if the Include Branches Filter is changed from the default * to a different value, PR's are not being built.
My understanding is that PR's should be built regardless of the branch filters specified.
Steps to reproduce:
- Create a new Multibranch Pipeline
- Choose Bibucket as the Source and specify the repo info as well as an Include Branches
- For example I specified: "master* PR*" to build the master + PR branches but nothing else
- Create a PR in the Bitbucket run the Branch Indexing
- Jenkins will not pick up the PR
- Modify the Include Branches back to the default of just a star * and Run Branch Indexing
- Jenkins will correctly pick up the PR
- If you modify it back to "master* PR*" Jenkins will again remove the PR job because it does not meet the criteria
- is related to
-
JENKINS-36548 Implement include and exclude filters for origin branches/PRs
-
- Resolved
-
- links to
We are also seeing this. There doesn't appear to be any help text for those include/exclude fields so I'm not sure how this is supposed to work. We'd also like something like "master PR*". Antonio Muñiz, should this be working or are we specifying this pattern incorrectly?