Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Checkout task for plan branch in deployment project not working

Sheila Szass
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 9, 2025

Hi,

I have a pretty normal setup with a build plan and an associated deployment project. For reasons, the build does not produce any artifacts, but instead just uploads an archive of the project on some server (this is different than the deployment server). After building we create a release and deploy it. The build plan uses a linked repository to checkout the code. Because there are no artifacts, the deployment project needs to checkout the project code. It does this using the checkout task. After the checkout, the project files are uploaded to the deployment server and some additional things happen that are not really relevant for the issue we're having.

The above works well, but it breaks when using plan branches. The build works fine when using a plan branch, but the deployment does not, because apparently the checkout task will checkout the code of the branch of the linked repository, and not the code of the plan branch, which is unexpected. 

Is this a bug in the checkout task or is this how it's suppose to work?  Is there some workaround other than manually checking out the code in a script task? 

We are using Bamboo Data Center 9.2 and we're building/deploying from a Docker container.

1 answer

0 votes
Tomislav Tobijas
Community Champion
January 16, 2026

Hi @Sheila Szass ,

I believe that this behavior, where the Bamboo deployment project's checkout task always checks out the branch from the linked repository, not the plan branch, is expected in Bamboo Data Center 9.2.

The checkout task in deployment projects does not automatically align with the plan branch used in the build plan.

Therefore, this is likely not considered a bug, but rather a limitation of how deployment projects and checkout tasks are designed to function.

A potential workaround would be to use a script task in your deployment environment to manually check out the correct branch. You could try Bamboo variables for this 👀

Here are two articles that might provide some additional insights on this:

Now, I've only played with Bamboo - haven't actually used it in a production environment, so potentially someone else knows more about this. 🤔

Cheers,
Tobi

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events