Automatic builds are no longer triggered after push commit on branch

ExportXMLWordPrintable

    • 937.3.10

      After upgrading the Bitbucket Branch Source plugin to version 937.3.9, we started receiving the following error message:

      2026-08-24 11:20:25.142+0000 [id=1132]	WARNING	j.s.a.SCMHeadEvent$DispatcherImpl#log: SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.MultiBranchProject$SCMEventListenerImpl@79748387 propagated an exception
java.lang.UnsupportedOperationException: Tag event of type UPDATE is not supported.
[LF]> Please fill an issue at https://issues.jenkins.io to the bitbucket-branch-source-plugin component.
	at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.impl.webhook.server.ServerPushEvent.getBranches(ServerPushEvent.java:418)
	at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.getBitbucketBranchesFromEvent(BitbucketSCMSource.java:423)
	at PluginClassLoader for cloudbees-bitbucket-branch-source//com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:371)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMSource._retrieve(SCMSource.java:368)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMSource.fetch(SCMSource.java:322)
	at PluginClassLoader for branch-api//jenkins.branch.MultiBranchProject$SCMEventListenerImpl.processHeadUpdate(MultiBranchProject.java:1653)
	at PluginClassLoader for branch-api//jenkins.branch.MultiBranchProject$SCMEventListenerImpl.onSCMHeadEvent(MultiBranchProject.java:1257)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:246)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:229)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMEvent$Dispatcher.run(SCMEvent.java:556)
	at jenkins.security.ImpersonatingScheduledExecutorService.lambda$wrap$0(ImpersonatingScheduledExecutorService.java:65)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)

      Since the upgrade, automatic Jenkins builds are no longer being triggered for many repositories when commits are pushed to Bitbucket. While the issue does not appear to affect all jobs, a significant number of repositories are impacted. This behavior was working correctly before the plugin update.

      A rollback to Bitbucket Branch Source version 937.3.8 immediately resolved the issue, and affected Jenkins jobs are once again triggered automatically after commits are pushed to Bitbucket.

            Assignee:
            Nikolas Falco
            Reporter:
            Christian Christ
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: