Adding a Bamboo Job implicitly adds a Repo Checkout Task?

[Matthew Kluber]

Hello Everyone,

I was adding a test job to my overall configuration for bamboo yaml specs and noticed something I didn't expect.

```

. . .

Hello World:
key: JOB2
tasks:
- script:
interpreter: SHELL
scripts:
- |-
echo "Hello World"
requirements:
- Computer.Name: TEST

```

Above is my job, that I've defined with a single script task in my bamboo-spec file on my bitbucket repository. Yet when I go to the configuration of the plan viewed as a yaml spec I see an extra task has been added?

From Yaml-Spec generated from plan:

```
. . .

Hello World:
key: JOB2
tasks:
- checkout:
force-clean-build: 'false'
- script:
interpreter: SHELL
scripts:
- echo "Hello World"
requirements:
- Computer.Name: TEST

```

any help would be appreciated. Thank you!

[C]

This isn't the best solution but I found that you can work around this by explicitly adding the Checkout task and making it dependent on a variable that you won't define.

For example:

 tasks:
 - checkout:
     force-clean-build: 'false'
     conditions:
       - variable:
           exists: NOPOP
     description: Checkout task
 
 # Now define your other tasks 

Also found this feature request:

https://jira.atlassian.com/browse/BAM-20709