Hi in your current nant task, add a target that creates a file somewhere, c:\temp\AppIsDirty.txt for example. when all goes well, use the built in nant propery : nant.onsuccess http://nant.sourceforge.net/release/latest/help/fundamentals/properties.html#built-in-properties
in this task, (executed from nant.onsuccess), delete c:\temp\AppIsDirty.txt in the publisher section, you can now execute a task, and check on this file, if so, clean up. with kind regards Ruben Willems On Wed, Sep 17, 2008 at 4:19 AM, Carnage <[EMAIL PROTECTED]> wrote: > > I have a ccnet project that builds a <nant> task where I have a > timeout value specifed as 3600 seconds. > > Recently this timeout period has started to be exceeded sometimes by > the job. > > In the case where a timeout occurs I need to do some extra cleanup - > specifically I need to revert some files that were checked out (opened > for edit) in Perforce. > > > When a nant task times out is there any way to detect this and run > another 'cleanup' nant task afterwards? > > > Any help appreciated, > > > Kind regards, > > Adam. >
