-
Bug
-
Resolution: Fixed
-
Major
-
None
-
-
937.0.3
After upgrading the Bitbucket Branch Source Plugin from 936.4.4 to 937.0.1, Jenkins fails to process Bitbucket webhook events. This is what we see Jenkins logs:
Sep 09, 2025 2:51:06 PM WARNING com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver getHookProcessor No processor found for the incoming Bitbucket hook. Skipping. Sep 09, 2025 2:51:06 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleException Caught unhandled exception with ID <id> java.lang.Exception: No processor found that supports this event. Refer to the user documentation on how configure the webHook in Bitbucket at https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/docs/USER_GUIDE.adoc#webhooks-registering at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:90) at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver.doNotify(BitbucketSCMSourcePushHookReceiver.java:120) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source)
In the Bitbucket webhook event logs
Request details Event type:pr:opened URL endpoint:https://jenkins.endpoint/bitbucket-scmsource-hook/notify?server_url=https://bitbucket.datacenter.endpoint Headers X-Request-Id: <id> Content-Type: application/json; charset=utf-8 X-Event-Key: pr:opened Body {...} Response details HTTP status:400 Headers X-Hudson-Theme: default Date: Tue, 09 Sep 2025 16:50:31 GMT X-Jenkins: 2.526 ...
Same for:
Event type:pr:from_ref_updated
URL endpoint:https://jenkins.endpoint/bitbucket-scmsource-hook/notify?server_url=https://bitbucket.datacenter.endpoint
Headers
Content-Type: application/json; charset=utf-8
X-Event-Key: pr:from_ref_updated
Response details
HTTP status:400
Ping works
Request details
Event type:Test connection event
URL endpoint:https://jenkins.endpoint/bitbucket-scmsource-hook/notify?server_url=https://bitbucket.datacenter.endpoint
Headers
X-Event-Key: diagnostics:ping
Response details
HTTP status:200
To reproduce
- Ideally use same environment as specified in the ticket
- In Manage Jenkins → System → Bitbucket Endpoints, the webhook implementation is set to "Native (Data Center)" with "Manage webhooks" enabled
- Trigger Jenkins /bitbucket-scmsource-hook/notify on Bitbucket pull request creation or update
- links to