-
Bug
-
Resolution: Unresolved
-
Minor
Bitbucket Server integration plugin set to trigger on Pull Request events only is supposed to run builds for branches for which specific PR event applies. However, it builds all the new commits for all the branches, not only for those with PR opened.
Let's consider a situation:
- A build plan in Jenkins using Bitbucket Server integration plugin set to trigger on Pull Request events only
- We have 4 branches in a repo: master, FEAT-1, FEAT-2, FEAT-3.
- We have one open PR: FEAT-3 -> master.
- We push a new commit to FEAT-1 - the build doesn't start
- We push a new commit to FEAT-2 - the build doesn't start
- We push a new commit to FEAT-3 - the build starts first for FEAT-1, then FEAT-2, and after that starts for FEAT-3
All the builds happen for the head commits of each branch.
Tested on:
Bitbucket 7.15
Bitbucket Server Integration 3.1
Hi Tomasz, thanks for raising the ticket
We've run this test with a few variations, but in no cases were we able to replicate the behaviour:
I'm wondering if this is a config issue. Can you share the job configuration xml, and if there's nothing sensitive, the build logs and jenkins logs?