Bamboo should fail builds when artifacts that are required can't be published due to size limits

Issue Summary

Bamboo has a feature that controls the size of artifacts copied back to its server once the builds finish running. If the artifact files exceed the size limit, they're not copied to Bamboo, and a warning is added to the result summary of the build that produced it to let users know what happened.

The problem is that builds are successful even when required artifacts are not copied back to Bamboo. Bamboo should fail builds when artifacts exceed the size limit and are required.

This is reproducible in Data Center:

Steps to Reproduce

1. Stop Bamboo.
2. Add the -Dbamboo.artifact.size.limit.per.build property to the JVM by following the instructions inside the "Configuring your system properties". This property has to be set in bytes. For example, if you want to limit the size of any single artifact file to 200 MB, you will need to use 209715200:

   -Dbamboo.artifact.size.limit.per.build=209715200
   

3. Start Bamboo.
4. Have a build plan produce a required artifact larger than 200 MB.

Expected Results

The build will fail because the artifact is required and couldn't be published as it exceeds 200 MB.

Actual Results

The build does not fail even though the artifact couldn't be published. A warning message is added to the build result summary page:

Unable to publish artifacts. Total artifact size for build [360 MB] exceeded limit [200 MB]. Artifacts were not copied to the server.

(28 June 2023, 1:24:26 PM, Agents: <agentName>)

Workaround

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