Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo Duplicate entries for produced artifacts



I recently migrated  Atlassian Bamboo (version 7.1.1 build 70117 - 23 Jul 20 ) to a new server . We now see that in all our build plans - the shared artifacts have two entries in Bamboo. 

One entry is grayed onether is a valid hyperlink to the artifacts.

I checked in the directory on Bamboo server that is denoted as "artifact location"  which is  "/var/atlassian/bamboo/artifacts/plan-136085508/shared/build-00512/"  . I see that there is a single set of artifacts actually generated.

I tried deleting and recreating the artifacts by editing build plan but this problem does not go away .

And addition to incorrect display another  unwanted fallout of this seems to be that my Bamboo Deployment plan is failing with following message 

"Unable to download artifact Non required shared artifact: [Debian Packages], pattern: [*.deb] anchored at: [uca-core/debian_packages]"

Does anyone knows how to deal with this ? Your suggestions are welcome 

Please let me know if I need to provide any additional input


See attached picture 

2 answers

1 accepted

0 votes
Answer accepted

This problem was finally resolved ( or should I call worked around :-) ) with help from  @ijeyanthan  of Atlassian support .  In Bamboo settings  go to Artifact Handlers page ( the Cogwheel --> Overview --> Artifact Handlers ) . In the  "Artifact Handlers" page there are checkboxes for making choices relating to artifact handlers . Among these the checkboxes for "Agent Local Handlers" were checked in my set-up (for both shared and non shared artifacts) . This choice was causing a duplicate line with a dead hyperlink for every artifact.  Unchecking the "Agent local artifact handler" check-boxes fixed the problem for me. 

So to me it seems like there could be a problem  in  "Agent local artifact handler" functionality  - but I don't care much about the artifact handlers being agent local and am happy with not using them to get rid of the duplicate entries .



I have the same situation. 

Planning to upgrade to latest and see


One interesting point,it's affected only for old artifacts to me. how about you?

Hi @Gonchik Tsymzhitov  thanks for your comment.  In my case this problem affects the freshly generated artifacts as well.

Do keep me posted if upgrade fixes it on your setup; so I may attempt an upgrade on my set-up as well 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

301 views 0 7
Read article

Atlassian Community Events