You should be able to setup a cron job that will remove any old builds within 30 days manually, provided it's running on Linux.
On Thursday, October 3, 2013 10:06:10 PM UTC+1, Christopher wrote: > I am looking at a Jenkins instance that has some issues. One of the things > I see is that while a top level job has its builds deleted after 30 days, > the sub module builds hang out forever. So I have a few projects that have > 3000 submodule builds each. Yikes! It eats up a lot of disk. > > My questions are: > Why don't the modules get cleaned up when the top level builds do. > Why doesn't the DIskUsage plugin doesn't report this. I have > one job that takes up 9 Gb of disk, but DiskUsage reports that it is using > a few hundred Mbs. Veru strange. > > Thanks, > Christopher > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/groups/opt_out.
