Bamboo build plan fails to start with RepositoryDefinitionException: Task failed since repository with id does not exist
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
Summary
Problem
Bamboo plan fails to start with RepositoryDefinitionException: Task failed since repository with id does not exist
Diagnosis
A stack trace similar to the following is found in the UI / error log after starting the plan:
com.atlassian.bamboo.repository.RepositoryDefinitionException: Task failed since repository with id 55836790 does not exist. It may have been deleted, please update the task and pick a new repository
at com.atlassian.bamboo.repository.RepositoryFunctions$IdSelectorToRepositoryDefinition.apply(RepositoryFunctions.java:96)Cause
This typically occurs when a linked repository is deleted from Bamboo Administration → Linked repositories while one or more plans still reference it in a Source code checkout task. The task retains the repository ID even after the underlying repository definition is removed, producing the id 55836790 does not exist error at build-start.
Solution
Your situation | Workaround |
|---|---|
You want to use a different repository (the original is genuinely deleted and no longer available) | Workaround 1: Remove and re-add the Source code checkout task; pick the new repository |
You want to keep using the same repository (it was re-added with the same name but a new ID) | Workaround 2: Re-save the repository settings (edit the title and save) to refresh the link type binding |
How to confirm the workaround worked
Run the plan manually (don't wait for a commit-triggered build).
Confirm the build progresses past the Source code checkout task without the
RepositoryDefinitionException.Check
<bamboo-agent-home>/logs/atlassian-bamboo.logfor normalVcsTaskExecutorentries instead of the stack trace.
How to prevent this in future
Before deleting a Linked repository, check which plans reference it via Bamboo Administration → Linked repositories → <repo> → Usages tab. Update or remove those plans' Source code checkout tasks first.
If you must delete a repository whose ID is referenced by many plans, consider a database backup before the delete operation in case the workaround steps below are needed at scale.
Was this helpful?