And of course, I found something right after sending this :) There's already an issue report <https://github.com/gocd/gocd/issues/879> on Github and a tool (gocd-janitor <https://github.com/ashwanthkumar/gocd-janitor>) that we'll be evaluating.
On Wed, Jun 29, 2016 at 10:13 AM Sofia Tania <[email protected]> wrote: > Hi, > > GoCD does not at the moment clean up artifacts and history when a pipeline > is deleted. Upon deletion, a warning is shown saying that there may be > problems if a pipeline with the same name is created in the future. > > Is this by design or is there something in the backlog that'll address > this? What would be the recommended way of cleaning them up? > > The particular issue we're seeing is that due to the branching model used, > there are lots of pipelines that have been deleted from the UI (as the > branches get merged / stale). The artifacts for these pipelines however > keep consuming gigabytes of space. We're considering writing our own > scripts to clean them up. > > Thanks, > Tania > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
