Bamboo yaml spec without Source Code Checkout Task

[Tobias Müller]

Dear Team,

We are currently using Bamboo version 9.2, and I would like to address an observation regarding the creation of Plans for a Repository using YAML specifications. It appears that a Source Code Checkout Task is automatically generated in each stage, even when it is not explicitly defined in the YAML spec.

Could you please confirm if this behavior is intentional? If so, could you provide the rationale behind it?

Additionally, we would prefer to replace the default Source Code Checkout Task with a Script Task for “git clone --depth=1”, for instance.

Thank you for your assistance.

[Shashank Kumar · Accepted solution]

Hi Tobias,

Welcome to Atlassian community

This is a expected behaviour, this task would be automatically added if a repository is linked to this plan. This is nothing related to specs but if you try to create the same plan using Bamboo GUI with a repository linked this would be the same behaviour.

Possibly the best solution would be to define the source code checkout task and disable it via YAML specs and then you can define the script task which you need.

Regards,

Shashank kumar

**please don't forget to Accept the answer if your query was answered**

[Tobias Müller]

Hi Shashank,

Thank you for your response. I accept that the behavior I described is expected, and I will go ahead and disable the default source code checkout task.

However, I would like to address the second part of your answer. I disagree with your assessment. In the Bamboo GUI, it is indeed possible to create a job without a source code checkout task by deleting the default task that is created. Unlike with a YAML specification definition, this task is not automatically recreated.

Regards,
Tobias

[Shashank Kumar]

Hello Tobias,

What I meant was If you have a repository linked in Bamboo and then if you add a new Job it will automatically add source code checkout task to the Job.

You can delete that manually, but that is a manual action. 

YAML specs will automatically add a source code checkout task as it will always find a repository, as manual actions are not available with YAML specs the best option is what I advised above.

This is the current design.

Regards,

Shashank Kumar