Best Option: Option D appears to be the most straightforward and effective solution that meets the requirements. It simplifies the process by utilizing CodeBuild's feature to directly send reports to an S3 bucket configured as the artifact destination. By setting the object expiration to 90 days in the S3 bucket settings, it fulfills the requirement to keep the test reports for 90 days. This option does not require additional services for moving the reports to S3, assuming the CodeBuild report group configuration allows for direct report storage in S3 with specified retention policies.

I think B

Not sure why we are configuring the report group as an artifact in the CodeBuild project buildspec file. Doesn't make sense and we use S3 lifecycle to expire objects automatically.

Both B & D seem to work, but object expiration settings still need to set the lifecycle rule manually for option D

answer D

Options B and D both provide viable solutions to meet the requirements. However, D offers a more direct and simplified approach by leveraging the capabilities of AWS CodeBuild and Amazon S3, including the use of S3 Lifecycle policies for managing the expiration of the test reports. Option B is also a valid solution but involves additional components like EventBridge and Lambda, which might not be necessary for this specific requirement. Therefore, D is the recommended solution for its simplicity and direct alignment with the requirements.

question key word : how to expire objects in S3. only S3 Lifecycle rule can expire objects.

rtifacts: files: - '**/*' name: '<artifact-name>' artifactPrefix: '<path-prefix>' discardPaths: yes baseDirectory: 'test-reports' reports: reportGroupName: files: - '**/*' baseDirectory: 'test-reports' Replace <path-prefix> with the desired path prefix within the S3 bucket.

AWS Lambda is not necessary. Test report files specified in the `base-directory` and `files` in the buildspec.yml reports section are uploaded to S3 by specifying them in the artifacts section as well. This is mean of `Configure the report group as an artifact in the CodeBuild project buildspec file.`

B is correct: <build process and outputs a test report.> means we need report group in codebuild and store report in S3 A: No mention of report group in codebuild C: No mention of s3 and report group D: report group is not the same as an artifact

B is correct

Pattern: run lambda inside PostBuild to zip up unit test result folder and copy to S3

https://malsouli.medium.com/10-smart-ways-to-use-aws-codebuild-22a8ee0d9302 The test reports have to be handled separately , either via postbuild, or via eventbridge as suggested in B

definitely B

"B. Add a report group in the CodeBuild project buildspec file with the appropriate path and format for the reports. Create an Amazon S3 bucket to store the reports. Configure an Amazon EventBridge rule that invokes an AWS Lambda function to copy the reports to the S3 bucket when a build is completed. Create an S3 Lifecycle rule to expire the objects after 90 days.": A test report expires 30 days after it is created. You cannot view an expired test report, but you can export the test results to raw test result files in an S3 bucket. Exported raw test files do not expire. https://docs.aws.amazon.com/codebuild/latest/userguide/test-report.html when you export a test group to s3, it is zipped https://docs.aws.amazon.com/codebuild/latest/userguide/test-report-group-create-cli.html

D might sound a better option but the problem is that "report groups" cannot be a part of artifacts. If you check the Buildspec syntax in the link below, you'll see that artifacts are separated from report groups. Under artifacts you cannot specify the arn of the report group. https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#reports-buildspec-file

D is correct.