Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Error: Unable to download artifact Shared artifact

I am using Shared artifact feature of bamboo to share files from build plan to deployment project.

But when I run deployment project I am facing error "Unable to download artifact Shared artifact"

Bamboo version I am using is 6.3.2

Kindly look into this on high priority.

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 27, 2019

Hi @Aditi7

Can you check if the artifact was published in the origin plan? You should see a message like this in your deployment logs "

...Preparing to download plan result: PROJ-PLAN-BUILD#

Do you think you can share the logs from PROJ-PLAN-BUILD# and from the deployment?
We only need the relevant part of it, the lines referring to the artifacts.

Deployment is taking old build no in 

.Preparing to download plan result: PROJ-PLAN-BUILD#

It is not taking latest build number 

Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 01, 2019

The deployment will always try to get the artifacts from a specific build (the build which was released). Every deployment will deploy a specific release. If you try to rerun a deployment it will keep trying to deploy that specific release, in other words, the same old build.

The message I shared can be found in your deployment logs and will tell you what exactly build is the one being deployed. Using that build key you can check if that build has the artifact you need or if for some reason the artifact was not deployed.

Another option is to deploy a new release. There are some ways to do it, so let me share them:

Create the release from the build result page and then deploy it 

  1. You create a new release, by navigating to the build result you want to deploy:
  2. Then click in Create release.
  3. Navigate to your deployment and select the option to Promote existing release to this environment

Create the release through the deploy page 

  1. Navigate to your deployment and select the option to Create a new release from build result


You can even configure your deployment to create a release for every successful build by adding an After successful build plan trigger into your deployment environment.

Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events