Artifact Cleanup by Pipeline

[Erik Helferty]

Apologies if this is something that has been discussed before, the only references I could see were a conversation from 2016, where gocd-janitor was suggested for artifact cleanup.

We've been using GoCD for about 3 years now, and our artifact store has grown to the point where it isn't manageable. For audit and customer requirement related reasons, we are required to keep build and testing artifacts for any of our releases that have gone live, but the built in cleanup doesn't support that requirement. gocd-janitor comes close, but requires manually updating the configuration if we add a new pipeline coming off our main branches. The vast majority of artifacts are off our development pipelines and we realistically never use anything but the latest successful build.

I think the ideal solution would be if there was a built-in configuration at the pipeline level to state how many successful artifacts to retain, similar to how gocd-janitor is set, but within the definition of the pipeline itself so that it is always set correctly.

[Aravind SV]

Hello Erik,

There’s a pull request in this area, which is open: https://github.com/gocd/gocd/pull/8311

Maybe you can add to that conversation there, so that the PR can accommodate what you’re thinking about.

Cheers,
Aravind

PS: There isn’t a pipeline-level config to retain a set number of artifacts.