Add report artifacts' links to release evidence
What does this MR do?
In #32773 (closed) we want to add links to "test results" to the release evidence.
By "test results" we mean artifacts created by the pipeline.
Since these artifacts need to be preserved from expiring, they can take significant storage space. To avoid this we only preserve "test report" artifacts - https://docs.gitlab.com/ee/ci/yaml/#artifactsreports.
Currently, artifacts will expire, in the next MR I plan to make them preserved. Also, if the evidence will be collected in the future in case of "upcoming release", some artifacts may already be expired. For we'll just mention this in the docs and create follow-up issue.
Extracted from !29255 (closed) which was too big for one piece, so I decided to split it into a few separate MRs.
Related to #32773 (closed)
Screenshots
https://www.youtube.com/watch?v=pfRzDvSBIWU
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team