Add reporting for release CodeBuild jobs

[dagnir]

Motivation and Context

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.

Description

Testing

Tested in personal account.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed
• A short description of the change has been added to the CHANGELOG
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[Bennett-Lynch]

This is cool! Is there anyway to integrate the test report directly into a PR, or do we have to open the CodeBuild console?

[abrooksv]

This is cool! Is there anyway to integrate the test report directly into a PR, or do we have to open the CodeBuild console?

Yes, CodeBuild launched public reports if you use the webhook, but have not tried it yet: https://aws.amazon.com/blogs/devops/introducing-public-builds-for-aws-codebuild/

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information