Hi there, I'm trying to integrate FxCop as part of our build process. We have a shared build script that developers run locally, and that our continuous integration server runs. As FxCop does not return failure error codes, I've implemented the method recommended by MS, in that if after analysis there's a report XML file, fire off the Nant <fail> task. This is fine when our build script is run locally, however, on our CI server (running CC.Net), this seems to fail the build in a very terminal way, so the output XML files don't get merged in the CC.Net <merge> task. Not too hot if the developer can't see what's failing the build on the CI server!
Can anyone suggest a workaround for this? I could knock up a quick standalone app, and call it with the CC.Net <exec> task, but I don't know if I can use status return codes to fail the build from there - the documentation isn't too hot. Cheers, James. ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
