Artifact Download task in Bamboo 5.12.x does not handle absolute path

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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


When running an Artifact download task, the path to the added under Destination path IS relative to the Working directory and does not accept absolute path by placing a forward slash at the begin of the path.

Destination path

Location that artifacts will be downloaded to, relative to the working directory

Please, refer to Sharing Artifacts documentation for further information.


Run Deployment that uses Artifact download task against a Bamboo remote agent, as a result you have:

Destination PathResulting on

files are downloaded to the directory /opt/temp


files are downloaded to the directory <bamboo-home>/xml-data/build-dir/819201-950273/opt/temp



Update Destination path by replacing forward slash

Go though all the Artifact download task that are misconfigured and provide them with the correct location, relative to the working directory.

Wait for Improvement Request to be addressed

There is an improvement request  BAM-16970 - Getting issue details... STATUS  filed addressing the issue in question.


Last modified on Nov 2, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.