bitbucket - Jenkins webhook works for only one job

Question

Its in the title. I have a webhook configured between Jenkins 2.222.1 and our bitbucket server v6.10.4. I can validate in bitbucket that the webhook is configured correctly, and this is doubly validated by the fact that on each commit, one of my multi-branch pipelines is triggered. I added a second multi-branch pipeline today, and can trigger it manually, but it does not trigger on commits. Is there any good way to debug this behavior? How can I track down whats going on? I'm taking over the responsibility for Jenkins from an outgoing colleague, so maybe he's configured something somewhere that would prevent new pipelines to be triggered (I asked him, he said he didn't think so).

Thanks for your help

Answer 1

等待大神答复