Which directory the commands/scripts are running when clone was disabled

Bitwise DEVS

clone:
  enabled: false

If we skip the cloning in a step then which directory the commands/script will run? Based on my observation, if cloning is enable all commands/scripts are running inside  

opt/atlassian/pipelines/agent/build

Does the build folder above still exist even clone is not enable?

If yes, then does it mean commands/scripts will run inside empty build folder?

If no, then how about if there are artifacts which means build folder will be created?

Syahrul

G'day, @Bitwise DEVS 

By default, with enable clone or disable the clone directory will always be point towards:

opt/atlassian/pipelines/agent/build

So if you disable the clone, the directory path will remain the same, but it will be an empty folder.

Regards,
Syahrul