My understanding is that everything on the agent is disposable once the agent has completed running its job. The way I have been handling it on my servers is to manually sort the contents of the pipelines directory by date and delete a bunch of the oldest ones to free up space whenever an agent runs too low.
I have been considering implementing a Scheduled Task (Windows agents) or cron job (Linux agents) to automatically delete anything older than a day or two. The time filter would prevent accidentally deleting the working folder of a pipeline that the agent is currently running. I haven't tried it yet but I don't see why it wouldn't work. Beyond that I, too, wonder what the recommended way of handling this is. Hope this helps, Jason On Tuesday, 13 November 2018 13:26:16 UTC-5, Jeff Vincent wrote: > > Out go-agent file systems are slowly filling up. All of the settings for > cleaning up disk space seem to be geared to server-specific storage of > artifacts and not agent-specific work spaces and I can't find anything in > the documentation about the agent storage needs or long-term maintenance. > > Can I just clear out the /var/lib/go-agent/pipelines/** folder on a > schedule, maybe via a cron job? What's the best practice? > > Thanks! > -- 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.
