Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to publish artifact [Latest JAR]: the source directory

Plan runs successful, artifact created, but

"No artifacts have been found for this build result."

is the message on the Artifacts tab.

In the error log:

19-Sep-2017 09:37:45Unable to publish artifact [Latest JAR]: the source directory /var/atlassian/application-data/bamboo/xml-data/build-dir/POTCLIENTMODULE-POTCLIENTMODULEPILOT-JOB1/build/libs/release does not exist.

 The missing directory existed before running the plan, but after running it was disappeared.

How to fix this?

2 answers

1 accepted

0 votes
Answer accepted

In the plan we have one stage with one default job. The job includes two tasks, source code checkout and gradle. The source code checkout directory can be specified in the source code checkout configuration. The working directory cna be specified within the Gradle configuration. The location can be specified in the Artifact definition.  The entered path in each configurations should be the same directory to avoid the error. For default location the path is not needed to define, so the fields in each configurations can be left empty.

Hi Jozsef,

  • If you re-create the directory can you reproduce the issue?

So this is showing us the source directory doesn't exist, so was it possibly cleaned up during the build run.

A build log might help to see what happened there.  If you can re-create the issue please do so and post the log snippet from the time you reproduced the issue. 

If you cannot take a look at the logs from the time the build occurred and see if there are any clues.  If nothing jumps out at you please post the log snippet here and we'll take a look.



Branden thank you for the suggestion, we already checked the logs, I described the solution below, which worked for us.

Suggest an answer

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

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

227 views 4 6
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you