Cannot fetch branch to source directory due to missing delta base

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Symptoms

The following appears in the atlassian-bamboo.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 2012-10-23 12:37:29,981 ERROR [3-BAM::PlanExec:pool-6-thread-3] [GitRepository] Failed to extract changesets, will return a stub changeset. com.atlassian.bamboo.repository.RepositoryException: Cannot fetch branch 'refs/heads/master' from 'file:///\\path\to\Git\Master\RepoName' to source directory 'path\to\bamboo_home\xml-data\build-dir\_git-repositories-cache\628be3a9be096f935bccf176e6cb02993a62ecfe'. Cannot fetch branch 'refs/heads/master' from 'file:///\\path\to\Git\Master\RepoName' to source directory 'path\to\bamboo_home\xml-data\build-dir\_git-repositories-cache\628be3a9be096f935bccf176e6cb02993a62ecfe'. Missing delta base 1136673d06115677871a829147f57088b160df5e at com.atlassian.bamboo.plugins.git.JGitOperationHelper.fetch(JGitOperationHelper.java:348) at com.atlassian.bamboo.plugins.git.JGitOperationHelper.fetch(JGitOperationHelper.java:288) at com.atlassian.bamboo.plugins.git.GitRepository$2.get(GitRepository.java:245) at com.atlassian.bamboo.plugins.git.GitRepository$2.get(GitRepository.java:240) at com.atlassian.util.concurrent.ManagedLocks$ManagedLockImpl.withLock(ManagedLocks.java:315) at com.atlassian.bamboo.plugins.git.GitRepository.collectChangesSinceLastBuild(GitRepository.java:239) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectionChangesWithRetry(DefaultChangeDetectionManager.java:384) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceLastBuild(DefaultChangeDetectionManager.java:260) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:218) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:136) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceLastBuildIfTriggered(DefaultChangeDetectionManager.java:113) at com.atlassian.bamboo.v2.trigger.ChangeDetectionListenerAction.process(ChangeDetectionListenerAction.java:100) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl$1$1.createBuildDetectionResult(ChainExecutionManagerImpl.java:176) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.createNewChainState(ChainExecutionManagerImpl.java:379) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.access$000(ChainExecutionManagerImpl.java:93) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl$1.getChainState(ChainExecutionManagerImpl.java:172) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.tryStartChainState(ChainExecutionManagerImpl.java:252) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.start(ChainExecutionManagerImpl.java:167)

Cause

The repository caches got corrupted.

Resolution

Option 1 (for modern versions of Bamboo)

  • Delete the repository caches on Cog icon > Overview > Repository Settings menu

Option 2

  • Shut down the Bamboo instance;

  • Delete the path\to\bamboo_home\xml-data\build-dir\_git-repositories-cache directory;

  • Restart the Bamboo instance;

  • Run the build again.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.