I've just converted a Pipeline job that built every time a change was pushed into BitBucket to the equivalent as a multibranch project.
Trouble is, pushes no longer trigger builds. BitBucket is still getting a 200 OK from the webhook when it hits Jenkins, but nothing else happens.
On inspection, the multibranch project created a `master` child job which has an option "Build when a change is pushed to BitBucket" but this is NOT checked, and the child job lacks any save button with which to change things. When I created the project the master branch built just fine first time.
This appears to be a bug but I might expect more complaints when I search for it. I wonder if it is some requirement of the user that connects to BitBucket - like it doesn't have sufficient rights for something not involving cloning?
Thoughts?
James