Similar situation here. Our server had a cron job cleaning up. I have now setup the Continuum Purge and can confirm on Monday if its working as expected.
-Murali. On Fri, Mar 25, 2011 at 3:33 PM, Louis Smith <[email protected]>wrote: > We have it configured - however, our SDI was on such a small box that there > were also CRON jobs running every few hours to "clean up" everything > possible... so we haven't been able to validate/verify if continuum is > doing > it correctly. > > Our new SDI box is a MUCH larger box, and we will configure this and can > begin testing - that should be 2 weekends from now if all goes well... > > Sorry I can't help right now. > > Louis > > On Fri, Mar 25, 2011 at 11:26 AM, Eric Fetzer <[email protected]> > wrote: > > > Nobody uses this functionality? > > > > > > > > On Mar 24, 2011, at 2:50 PM, Eric Fetzer <[email protected]> wrote: > > > > > I've set up our purge configuration as follows: > > > > > > releases: > > > Days Older "15" > > > Retention Count "2" > > > Delete All "false" > > > Schedule "Purge_Files" > > > Default "false" > > > Enabled "true" > > > > > > buildOutput: > > > Days Older "15" > > > Retention Count "2" > > > Delete All "false" > > > Schedule "Purge_Files" > > > Default "false" > > > Enabled "true" > > > > > > All of my builds go every single night, so Retention can't be messing > me > > up. When I look at the buildOutput area, I see lots of files over 15 > days > > old: > > > > > > [continuum@penguin] > > /opt/continuum/apache-continuum-1.3.6/data/build-output-directory-> find > ./ > > -mtime +15 | wc > > > 178 178 3189 > > > In fact, there are quite a few over 30 days old: > > > > > > [continuum@penguin build-output-directory]$ find ./ -mtime +30 | wc > > > 115 115 2055 > > > > > > Is there something I'm doing wrong? > > > > > > Thanks, > > > Eric > > > > > > > > > -- > Dr. Louis Smith, ThD > Chief Technology Officer, Kyra InfoTech > Colonel, Commemorative Air Force >
