Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Sharing previous build artifact is failing

sulekhak January 4, 2024

I have a plan A and has Stage 1 and Stage 2
Stage 1 has 1 Job which creates artifact in the working directory
Stage 2 has 1 Job which downloads those files and uses those files in the execution flow

Have disabled Stage2 and ran stage 1 and files are shared in the working directory
Have disabled stage 1 and ran Stage 2 but not able to use the shared files, shared files are present in the directory.

1 answer

1 vote
Shashank Kumar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 7, 2024

Hello sulekhak,

Welcome to Atlassian community.

When you run stage 1 Artifacts are created in the working directory of the agent where you ran the Build and once the Job is completed, these artifacts are then published to Bamboo server.

You can see this information in the build logs of the Job from Stage 1 as below

08-Jan-2024 06:22:34 Running post build plugin 'Artifact Copier'
08-Jan-2024 06:22:34 Publishing an artifact: Artifact1
08-Jan-2024 06:22:34 Finished publishing of artifact Required shared artifact Http Compression On : [Artifact1], patterns: [*.jar] in 64.49 ms

When you go to the Artifacts tab of the Job which created this artifacts, you'll see where it is stored on the Bamboo server

Shared artifacts can be found under:


Now if you disable Stage 1, Artifcats won't be created for that particular run as Stage 1 is disable and Stage 2 won't able to download it.

You can't share artifacts across different build runs.

Same concept is applicable if you are create dependency from Artifacts from Stage 1 to Stage 2 via


Shashank Kumar

**please don't forget to Accept the answer if your query was answered**

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events