Skip to content

Remove coverage reports from S3 release

Tomasz Maczukin requested to merge remove-coverage-report-from-s3-release into main

What does this MR do?

Removes the coverage report from the release sent to the S3 bucket.

Why was this MR needed?

We've added that in the past because it was the only reliable way to store coverage report for a longer period. Nowadays it's not needed as:

  • we have the report integrated to GitLab's UI with cobertura,
  • artifacts for the last job from the branch should be stored without expiration.

So the reviewer will be able to check the details without a need to store them on S3.

At the same time it feels strange that our S3 bucket contains binaries, packages, images, checksums - all things that naturally feel to be a part of a release. And a coverage report, which for a regular user have no meaning.

What's the best way to test this MR?

What are the relevant issue numbers?

Edited by Tomasz Maczukin

Merge request reports