Bamboo build isn't triggered after upgrading Bitbucket Server

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

After upgrading Stash to Bitbucket Server, Bamboo build isn't triggered by new commits anymore

The following appears in the atlassian-bitbucket.log

2015-12-24 11:37:04,826 ERROR [AtlassianEvent::thread-2] 43839099 @3T1RHLx697x35631x0 1pjmlnm 196.168.1.112 SSH - git-receive-pack '/project/repo.git' c.a.e.i.AsynchronousAbleEventDispatcher There was an exception thrown trying to dispatch event [com.atlassian.stash.plugin.remote.event.StashRepositoryRefsChangedEvent@7611b653[cloneLinks=[CloneLink{name=http, href=http://43839099@localhost/scm/project/repo.git}, CloneLink{name=ssh, href=ssh://git@localhost:7999/project/repo.git}],repositoryProject=PROJECT,repositorySlug=repo,committer=43839099,sourceId=<null>,sourceUrl=<null>]] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.event.remote.impl.RemoteEventListener.onRemoteEvent(com.atlassian.event.remote.RemoteEvent), listener=com.atlassian.event.remote.impl.RemoteEventListener@56642188}]
java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/atlassian/devstatus/vcs/LimitExceededEvent
	at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54) [atlassian-event-3.0.0.jar:na]
	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:46) [atlassian-event-3.0.0.jar:na]
	at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299) [guava-18.0.jar:na]
	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:105) [atlassian-event-3.0.0.jar:na]
	at com.atlassian.event.internal.LockFreeEventPublisher$Publisher.dispatch(LockFreeEventPublisher.java:260) [atlassian-event-3.0.0.jar:na]
	at com.atlassian.event.internal.LockFreeEventPublisher.publish(LockFreeEventPublisher.java:102) [atlassian-event-3.0.0.jar:na]
	at com.atlassian.stash.internal.event.TransactionAwareEventPublisher.publish(TransactionAwareEventPublisher.java:84) [bitbucket-platform-4.2.0.jar:na]
	at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:30) [atlassian-plugins-core-4.0.4.jar:na]

Cause

Bitbucket Server is still using an old plugin cache.

Resolution

  1. Shutdown Bitbucket Server
  2. Delete the following directories:
    • <BITBUCKET_SERVER_HOME>/plugins/.osgi-cache
    • <BITBUCKET_SERVER_HOME>/plugins/.bundled-plugins
  3. Restart Bitbucket Server
Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.