Within your config file, you can opt to upload build artifacts using the
store_artifacts key and specifying a path to upload.
These artifacts are then able to be downloaded on the artifacts tab or via the API. The download link in both cases is constructed of two parts, the first part of the URL is where we are hosting it:
While the second part of the URL is the path you specified in the
So altogether the URL would look something like:
Because of this if you had your
store_artifacts step set to:
- store_artifacts: path: ../project/app/test
This would still successfully upload the artifacts but they would in turn not be available via the UI or API as
.. within a URL is interpreted as a null value.
To both successfully upload the artifacts and make them available for download use a path like this:
- store_artifacts: path: ~/project/app/test
- store_artifacts: path: root/project/app/test