[JENKINS-70772] Multi-branch scan is no more triggered by webhook after update

Multi-branch scan is no more triggered by webhook after update to Jenkins 2.375.2 and latest plugin-versions at that time.

Before the update: when a new branch was pushed to BitBucket, the scan was triggered immediately and automatically. Now the developers are puzzled why their new banch is not found in Jenkins after they pushed. As a workaround, we configured the poll to minimal value of 1 min, but it's still a nuisance for the developers.

We are using the generic webhook in BitBucket and it's pointed to the "git/notifyCommit"-endpoint in jenkins. The webhook is otherwise working: the jobs that we have allowed to do "automatic SCM triggering" are getting automatically built.

Because of the update, we had to add the token to the webhook url, because of the some security fix in Jenkins. We are suspecting whether the token-related changes in Jenkins/plugins broke the automatic rescan ( a long shot from us, yes, sorry for that).

While troubleshooting and searching if this is a known defect, we found out about "Multibranch Scan Webhook Trigger"-plugin. We have never had that installed, and never knew about it -because the scan was already automatically triggered by the webhook. if that's the way to go, then we'll walk it. But, there seems to be some regression, because earlier the scan was working without additional plugins. Also picked Major as it seems like a regression in LTS, but I'm not sure about the Jenkins project conventions.

I really don't know which component provides the functionality. I had to choose one, so I picked "pipeline". That could be wrong, of course.

---
Originally reported by karniemi, imported from: Multi-branch scan is no more triggered by webhook after update

• status: Open
  
• priority: Major
  
• component(s): workflow-multibranch-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251212-090250
  

Raw content of original issue

Multi-branch scan is no more triggered by webhook after update to Jenkins 2.375.2 and latest plugin-versions at that time.


Before the update: when a new branch was pushed to BitBucket, the scan was triggered immediately and automatically. Now the developers are puzzled why their new banch is not found in Jenkins after they pushed. As a workaround, we configured the poll to minimal value of 1 min, but it's still a nuisance for the developers.


We are using the generic webhook in BitBucket and it's pointed to the "git/notifyCommit"-endpoint in jenkins. The webhook is otherwise working: the jobs that we have allowed to do "automatic SCM triggering" are getting automatically built.


Because of the update, we had to add the token to the webhook url, because of the some security fix in Jenkins. We are suspecting whether the token-related changes in Jenkins/plugins broke the automatic rescan ( a long shot from us, yes, sorry for that).


While troubleshooting and searching if this is a known defect, we found out about "Multibranch Scan Webhook Trigger"-plugin. We have never had that installed, and never knew about it -because the scan was already automatically triggered by the webhook. if that's the way to go, then we'll walk it. But, there seems to be some regression, because earlier the scan was working without additional plugins. Also picked Major as it seems like a regression in LTS, but I'm not sure about the Jenkins project conventions.


I really don't know which component provides the functionality. I had to choose one, so I picked "pipeline". That could be wrong, of course.

Start with the workflow-multibranch-plugin handling of Jenkins's git/notifyCommit endpoint and the tokenized webhook request described in the issue. Compare the behavior before and after the Jenkins and plugin updates; done means a new BitBucket branch triggers a multibranch scan without polling or an additional trigger plugin.

Written by the indexing model from the issue text.