Unable to publish artifact (no error)


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.

5 answers

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:


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

No, sorry, I never did.

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.

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


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

807 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you