Issue Summary

When an Artifact copier task in a build fails, the build continues to show as successful even though the Artifact copy task failed (for instance, due to OOME).

Steps to Reproduce

1. We weren't able to reproduce, but when we find an error like below in the build log (in this case it is OOME) just before the build outcome.

   simple	08-May-2021 16:21:27	Finished publishing of artifact Non required shared artifact: [sample], pattern: [**/*] anchored at: [sample] in 2.8 min
   simple	08-May-2021 16:21:27	Publishing an artifact: artfname
   error	08-May-2021 16:43:27	Failed to execute plugin 'Artifact Copier' with error: Java heap space
   

• Build status is still a success.

Expected Results

The build fails as the artifact transfer activity has failed.

Actual Results

when post build plugins were running, the build status is not changed in response to errors like below appearing in the meantime.

error	08-May-2021 16:43:27	Failed to execute plugin 'Artifact Copier' with error: Java heap space

The below exception is thrown in the atlassian-bamboo.log file:

2021-05-08 16:42:13,974 ERROR [12-BranchDetectionBackgroundThread:pool-19-thread-3] [SystemAuthorityThreadFactory] Uncaught exception in thread 12-BranchDetectionBackgroundThread:pool-19-thread-3
 java.lang.OutOfMemoryError: Java heap space
 2021-05-08 16:42:19,869 ERROR [httpclient-io:thread-1] [InternalHttpAsyncClient] I/O reactor terminated abnormally
 org.apache.http.nio.reactor.IOReactorException: I/O dispatch worker terminated abnormally
 at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:356)
 at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221)
 at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
 at java.lang.Thread.run(Thread.java:748)
 Caused by: java.lang.OutOfMemoryError: Java heap space
 

Workaround

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