If not, your build script (Maven, Gradle, Ant, etc.) likely failed to generate the file, or the in the Artifact definition is incorrect.
The build result still exists, but the physical artifact files have been cleaned up by Bamboo’s "Expiry" settings, leaving the deployment project reaching for a ghost file. Step-by-Step Solutions 1. Verify Artifact Production
Check the build logs to see if the file was created. If not, your build script (Maven, Gradle, Ant, etc
There is a checkbox (or setting depending on your Bamboo version) for .
First, check the tab of the specific Build Result that triggered the failure. Is the artifact actually listed there? Verify Artifact Production Check the build logs to
Ensure you haven't selected "All Artifacts" if some of those artifacts are optional and weren't created in the latest build.
If this is happening during a , the issue is usually in the Artifact Download Task : Go to your Deployment Project > Edit Environment > Tasks . Locate the Artifact Download task. Is the artifact actually listed there
Ensure your global "Artifact Expiry" isn't deleting files before the deployment starts.