Hi Thats good to know,
now the big question : should the artifact cleanup remove the read-only bit? the bit is there for a reason ;-) maybe we can skip the readonly files, but continue on deleteing other ones, and report that file X was not deleted becaus it was readonly. What do you think? with kind regards Ruben Willems On Wed, Jan 14, 2009 at 3:33 PM, markk <[email protected]> wrote: > > Hi Ruben: > > Changing the properties (no read only) worked for me. > > Thanks for the help. > > Mark K > > On Jan 13, 4:46 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > this works for me, > > logDir specified or not, or you sure that you do not see anything in the > > console window? > > I did notice that when there is a read only file in the log dir, the > > deletion stops. > > > > with kind regards > > Ruben Willems > > > > On Tue, Jan 13, 2009 at 9:28 PM, Ruben Willems <[email protected] > >wrote: > > > > > Hi > > > > > this should not happen, I'll look into it > > > > > with kind regards > > > Ruben Willems > > > > > On Tue, Jan 13, 2009 at 6:45 PM, markk <[email protected]> > wrote: > > > > >> Hi All: > > > > >> I have successfully set up cc.net 1.4.2.14 and want to take advantage > > >> of the Artifact Cleanup task. I have it in my ccnet.config as such: > > > > >> <publisher> > > >> <xmllogger logDir="pathtobuildlog"/> > > >> <!-- this is where to add artifact cleanup publisher task --> > > >> <artifactcleanup cleanUpMethod="DeleteBuildsOlderThanXDays" > > >> cleanUpValue="7"/> > > >> <publisher/> > > > > >> To date I haven't seen ANY cleanup happening. The log files still > > >> exist as they did prior to the build. I haven't seen any errors > > >> either. > > > > >> Can anyone give me a clue as to what I am doing wrong? > > > > >> Thanks > > > > >> Mark K >
