Create a retention policy for job logs
Proposal
Following up from Determine if Job Logs count towards artifact st... (#373917 - closed) we have determined:
- Job logs are part of the artifacts storage and
- Jobs logs do not currently have a retention policy (no expiration) and are difficult to manage
As part of &8715 we need to add functionality to enable customers visibility and user-friendly options to view and delete these job artifacts and traces. We currently have one API allowing for deletion: https://docs.gitlab.com/ee/api/jobs.html#erase-a-job.
There are multiple potential solutions. This issue addresses the first item only.
- Introduce a retention policy which expires job logs after a certain period (i.e. 7 days) for auto deletion.
- Add functionality for search/sort/removal as part of the new Artifacts page. This solution is being addressed separately in Delete an artifact on artifacts page (#370150 - closed) and Browse artifacts of all types from artifacts page (#370151) and Ability to filter and batch delete artifacts di... (&1974 - closed).
- Updated API for bulk removal action. This solution is detailed in Follow-up: Introduce Parameters to bulk delete ... (#14495) and will be implemented in Frontend: Artifacts bulk delete: make "select a... (#396792 - closed)
Links
Edited by Max Orefice