nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Jozsef Lehocz

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?

Accepted answers

Jozsef Lehocz

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.

All comments

somethingblue

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.

Cheers,

Branden

Jozsef Lehocz

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