-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins ver. 2.89.1 / bitbucket-branch-source-plugin ver. 2.2.3 (also checked 2.2.7)
A few weeks ago webhooks stopped trigger build for one project. In Jenkins logs I see only this exception:
Dec 11, 2017 1:53:37 PM jenkins.scm.api.SCMHeadEvent$DispatcherImpl log Dec 11, 2017 1:53:37 PM WARNING: SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.MultiBranchProject$SCMEventListenerImpl@685907be propagated an exception Dec 11, 2017 1:53:37 PM java.lang.NullPointerException at com.cloudbees.jenkins.plugins.bitbucket.hooks.PushHookProcessor$1.heads(PushHookProcessor.java:163) at jenkins.scm.api.SCMHeadEvent.isMatch(SCMHeadEvent.java:138) at jenkins.branch.MultiBranchProject$SCMEventListenerImpl.processHeadUpdate(MultiBranchProject.java:1392) at jenkins.branch.MultiBranchProject$SCMEventListenerImpl.onSCMHeadEvent(MultiBranchProject.java:1170) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:247) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:230) at jenkins.scm.api.SCMEvent$Dispatcher.run(SCMEvent.java:481) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
How to enable, maybe, some debugging for this plugin?
I don't sure if it related, but request body for this webhooks now >1100574 bytes and it is much more then for other our projects.
