Keep the most recent PipelineArtifact forever
Problem
As explained on our documentation, our system now keeps the most recent artifact.
By default, the latest artifacts from the most recent successful jobs are never deleted. If a job is configured with expire_in, its artifacts only expire if a more recent artifact exists.
This is not the case for PipelineArtifact
which are automatically purged from the system after 1 week.
Proposal
We should refactor our PipelineArtifact
purge mechanism to keep the most recent artifact and replicate the same behaviour we have with JobArtifact
.
This is currently happening for 2 reports type:
We could either inherit the same expiration date which is defined at the JobArtifact
level or simply keep the most recent artifact by default.
Edited by Max Orefice