Hi
CCNet's exec task is ok, I just tested it again with the following test programs (2 console programs): consok code in the main Environment.ExitCode == 0; consNotOk code in the main Environment.ExitCode == 1; and when I placed these in CCNet, the build was OK for consok and the build failed for consNotOk So there must be a problem with your config, or the tasks really fail with kind regards Ruben Willems On Thu, Mar 19, 2009 at 2:32 PM, Michal Dabrowski < [email protected]> wrote: > > Hi, > > yesterday I've updated my CCNet to 1.4.3. Today I've noticed that > CCNet no longer recognizes failures of exec tasks. This actually > applies to <exec> and <rake> tasks. Every build is successful, even if > the rake aborts or the exec tasks fail. Most of my CCNet configuration > remained the same as before the upgrade (after upgrade I've only > replaced msbuild with rake, but these mentioned exec tasks weren't > touched at all). Did anyone else encounter such behavior? > > Regards, > Michal Dabrowski >
