Open mafidchao opened 7 years ago
Hit this issue today as well. Test button triggers build for repository with branch that is set as default in the repository settings (in my case develop)
I found the solution was to tick the "omit branch name" in BitBucket and check that "Poll SCM" option was enabled in the job configuration (even though the schedule is then left empty).
When using the Trigger Jenkins button to test configuration, if there is no job that is set to build the master branch, this red text appears:
And if there is a job that builds the master branch, the trigger appears to only send a notification for that branch and no others.
The post-receive functionality still works as normal for configured branches, so this just makes testing a little inconvenient
Using webhook 3.0.1 and Bitbucket 4.10.2
This appears to have been brought up in #161 and #147 , just opening an issue for this specific problem