Add reporting for release CodeBuild jobs (#2833)

Trawling through the logs looking for the tests that failed is time consuming,
especially because tests are run in parallel, making the logs harder to follow.
This uses the test result dashboarding feature from CodeBuild to make it much
easier and faster to find tests that failed during a release.

Author: dagnir

buildspecs/build.yml

@@ -15,4 +15,11 @@ phases:
           cd test/module-path-tests
           mvn package
           mvn exec:exec -P mock-tests
-        fi
+        fi
+    finally:
+      - mkdir -p codebuild-test-reports
+      - find ./ -name 'TEST-*.xml' -type f -exec cp {} codebuild-test-reports/ \;
+reports:
+  UnitTests:
+    files:
+      - 'codebuild-test-reports/**/*'

buildspecs/integ-test.yml

@@ -23,4 +23,11 @@ phases:
           cd test/module-path-tests
           mvn package
           mvn exec:exec -P integ-tests
-        fi
+        fi
+    finally:
+      - mkdir -p codebuild-test-reports
+      - find ./ -name 'TEST-*.xml' -type f -exec cp {} codebuild-test-reports/ \;
+reports:
+  IntegTests:
+    files:
+      - 'codebuild-test-reports/**/*'

buildspecs/stability-test.yml

@@ -7,4 +7,11 @@ phases:
 
   build:
     commands:
-      - mvn clean install -P stability-tests -pl :stability-tests --am
+      - mvn clean install -P stability-tests -pl :stability-tests --am
+    finally:
+      - mkdir -p codebuild-test-reports
+      - find ./ -name 'TEST-*.xml' -type f -exec cp {} codebuild-test-reports/ \;
+reports:
+  StabilityTests:
+    files:
+      - 'codebuild-test-reports/**/*'