Document default report artifact expiration times for testing related reports
Problem to solve
Users rely on reports generated by testing features (code quality, junit test reports, etc.) to be present for various audit and compliance tasks. It is not clear when these reports will expire and the historic record in the Merge Request disappear with it.
Further details
Data will be packaged up for users as part of release evidence at some point. Until then documentation for these reports should be more explicit about when the reports expire and what will happen when they do.
This includes but may not be limited to:
Proposal
Update documentation page noted above with clear explanation:
- How long the default expire_in value is from the template
- How to override the default
- Expected behavior of an MR widget when that report expires.
Who can address the issue
Anyone in grouptesting or anyone who looks it up in the projects and submits MRs
Other links/references
Edited by James Heimbuck