Artifact Download task in Bamboo 5.12.x does not handle absolute path
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Problem
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.
Diagnosis
Run Deployment that uses Artifact download task against a Bamboo remote agent, as a result you have:
| Destination Path | Resulting on |
|---|---|
| /opt/temp | files are downloaded to the directory /opt/temp |
| opt/temp | files are downloaded to the directory <bamboo-home>/xml-data/build-dir/819201-950273/opt/temp |
Workaround
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 - Fix absolute paths for artifacts being changed to relative paths filed addressing the issue in question. This has now been implemented in Bamboo version 5.12.4, 5.13.0.1 and later