Stronger validation on artifact transfer copy operation(moveArtifactToGlobalStorage) when copying artifacts to globalStorage

Issue Summary

Artifacts will be moved to the <Bamboo-Home>/artifacts/globalStorage folder under the following conditions:

• the shared artifact generated by a build has been consumed by a Deployment (Sharing artifacts from a build plan to a deployment environment) AND;
• the build result that originally produced the shared artifact has been deleted (Deleting the results of a plan build) OR expired (Configuring global expiry or Configuring expiry of a plan's job build results).

When there are failures while copying artifacts to globalStorage, Bamboo does not throw exceptions or error messages in the server logs about the artifact copy operation failure, and it removes the artifacts from the <Bamboo-Home>/artifacts folder.
 

This is reproducible on Data Center:

Steps to Reproduce

This issue is observed when using AWS S3 as an artifact handler type in Bamboo.

Expected Results

If there is any failure in artifact transfer from the original artifact folder to the global storage folder, Bamboo should throw exceptions about the artifact transfer failure reason. And also, Bamboo should not remove the artifact from the <Bamboo-Home>/<artifact-folder> if there is any failure of artifact copy to globalStorage.

There should be stronger validation of the copy operation for artifact transfers to the globalStorage folder.

Actual Results

Bamboo doesn't throw any exceptions in the atlassian-bamboo.log file about the artifact transfer failure and also removes the artifact from the <Bamboo-home>/<artifact-folder>, even though the artifact was not copied to the globalStorage path.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available