Hi it is normal that when a task fails, all other tasks will not get ran. but judging from your mail, it is not the case in your setup.
The only reason can be that ccnet does not know that the task is failed, CCNet detects this by looking at the exit codes of the executable non zero are error if the program displays something like : KABOOM ERROR on the screen, but returns a zero as the exit code, CCNet considers it as being succesfull to check if this is the case, run your command with the arguments as you pass in CCNet in a command window. Do this on a situation you know that should fail. Next run the following command : echo %errorlevel% what do you get? with kind regards Ruben Willems On Fri, Jul 24, 2009 at 4:57 PM, GHarmonDDVA < [email protected]> wrote: > > I have the following tasks in a task block. If one of them fails, I > want the execution flow to stop instead of going to the next <exec>. > But, I can't find a way to stop if one of the previous <exec>'s has > failed. Any information would be greatly appreciated. > > > <tasks> > <exec> > > <executable>c:\BuildTest\RTS.exe</executable> > <buildArgs>/s:55/qcbin /n:DCS_REL /d:QTP_REL > /u:ghn /p:***** / > f:Root\QAREL /t:Open_Close /l</buildArgs> > > <buildTimeoutSeconds>1200</buildTimeoutSeconds> > </exec> > > <exec> > > <executable>c:\BuildTest\RTS.exe</executable> > <buildArgs>/s:55/qcbin /n:DCS_REL /d:QTP_REL > /u:ghn /p:***** / > f:Root\QAREL /t:Load_DCS /l</buildArgs> > > <buildTimeoutSeconds>120</buildTimeoutSeconds> > </exec> > > <exec> > > <executable>c:\BuildTest\RTS.exe</executable> > <buildArgs>/s:55/qcbin /n:DCS_REL /d:QTP_REL > /u:ghn /p:***** / > f:Root\QAREL /t:Button_Click /l</buildArgs> > > <buildTimeoutSeconds>9900</buildTimeoutSeconds> > </exec> > > <exec> > > <executable>c:\BuildTest\RTS.exe</executable> > <buildArgs>/s:55/qcbin /n:DCS_REL /d:QTP_REL > /u:ghn /p:***** / > f:Root\QAREL /t:Email_BC_Results /l</buildArgs> > > <buildTimeoutSeconds>1800</buildTimeoutSeconds> > </exec> > </tasks> >
