<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=593716) </details> <!--IssueSummary end--> This feature proposal was created on behalf of a ~"GitLab Ultimate" customer who expressed their interest in a [support ticket](https://gitlab.zendesk.com/agent/tickets/701779) (internal link) <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Currently, it's possible to enable `Keep artifacts from latest successful pipelines` to keep artifacts from the latest successful pipeline for each branch/tag in a repository. For some use cases, this setting may need to be disabled at an instance or project level, for example due to large artifacts consuming storage space. It would be useful if there was the ability to keep only security report artifacts / `artifacts:reports` on each branch/tag. This would allow the latest pipeline on each git branch or tag to contain its respective security report artifacts. This ensures that compliance centre checks succeed (as they check for non-expired artifacts on the latest pipeline) <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->