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

Unable to publish artifact (no error)

Philip Rittenhouse May 22, 2014


I am trying to create a simple artifact to share a source tree between stages. This is just a simple test to help me better understand how Bamboo works.

I have Location set to "fw_comp" which is the Checkout Directory I have configured for the Source Code Checkout task. The Copy Pattern is **/* so I expect the full fw_comp tree to be copied into the artifact.

When I run I get the following error in the log. From what I have read, the error "Unable to publish artifact" is usually followed by some kind of reason but mine is just blank. Any idea what this means? This is a fresh install of Bamboo and we are all new to this tool so I am wondering if this indicates some kind of configuration problem rather than a problem with my plan config.



20-May-2014 14:46:20

Finished task 'Check out fw_comp from head of mainline R12.X branch (master as set in Project repositories)'

20-May-2014 14:46:20

Running pre-build action: VCS Version Collector

20-May-2014 14:46:20

Running pre-build action: Clover Grails PreBuild Action

20-May-2014 14:46:21

Running post build plugin 'Artifact Copier'

20-May-2014 14:46:21

Publishing an artifact: Firmware Repository

20-May-2014 14:46:46

Unable to publish artifact [Firmware Repository]:

20-May-2014 14:46:46

The artifact is required for down stream Stages and Jobs, build will now fail.

6 answers

1 vote
david_0187 August 9, 2019

I have to say, Bamboo looks very nice when it's working - but I am appalled at this and other failures. This has been an issue since 2014 and I have a similar problem today.

I am setting Location to . and Copy pattern to * and I get the following in the logs after a successful build:


Unable to publish artifact [name]: 


That's it. No explanation. 400GB+ free space as Frederik suggested could be a problem. @Matt Allen3 I would think my permissions are correct for the "." directory relative to the build working directory. I tried **, **/*, **/**, **/*.*. I also tried known directory names instead of .

I have a solution:

Jeff Everett February 20, 2020

These kind of useless error messages make working in bamboo very frustrating.  Tailing build agent's log files to troubleshoot build errors is decidedly un-cool.

1 vote
Frederik November 21, 2017

I found that artifact publication can fail without an error if there is not enough disk space on the server (if using local storage). You can check the "Disk space free" on the "System information" page in your Bamboo configuration.

I added an improvement request to fix this:

0 votes
Mika Nokka October 4, 2015

In my case the solution, when finally found, was this:

I had used Artifact copy pattern "maven_*.jar". For some reason, the build was generating  the .jar file without the prefix maven. So by changing copy pattern to "*.jar", the artifact was found and passed ok into downstream


0 votes
Matt Allen November 10, 2014

I have experienced this same problem recently. For me, the solution was to check the file and folder permissions of the artifact folder on the bamboo server, and make sure that the user running the bamboo server had ownership.

0 votes
Philip Rittenhouse October 9, 2014

No, sorry, I never did.

0 votes
Brandon Vulaj October 9, 2014

@Philip Rittenhouse - Did you ever find a solution to this?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events