[NCrunch Console Tool v3.10.0.6]
Is there a way I can avoid running tests if NCrunch reports compile error?
(I don't want to hold up the build server by running tests if the build is already set to fail. The only workaround I see is to have a separate compile step with msBuild, and avoid calling NCrunch if it fails).
Thanks.
Daily Usage Issues
ConsoleTool: Not run tests if build is failing?
Started by GreenMoose on 5,924 views
Remco NCrunch Developer
#11195
12 Sep 2017 07:22 UTC
There isn't anything in NCrunch that can be configured to do this. The engine will always build what it can, then run tests with whatever assemblies it managed to build.
Having a separate compile step before running NCrunch is one way to do this. An alternative would be to rig something up to capture the output from the NCrunch engine and examine this for build errors, terminating the process if any are detected. This could also be expanded to include test failures if you wanted to truncate the run on other conditions.
Having a separate compile step before running NCrunch is one way to do this. An alternative would be to rig something up to capture the output from the NCrunch engine and examine this for build errors, terminating the process if any are detected. This could also be expanded to include test failures if you wanted to truncate the run on other conditions.
Remco wrote:An alternative would be to rig something up to capture the output from the NCrunch engine and examine this for build errors, terminating the process if any are detected.
I had this in mind as well bug figured the NCrunch workspace will be left uncleaned, does NCrunch do something smart with workspace/cachefolder leftovers so it cleans them eventually even if I simply kill the process now and then?
Remco NCrunch Developer
#11197
12 Sep 2017 09:54 UTC
GreenMoose wrote:
I had this in mind as well bug figured the NCrunch workspace will be left uncleaned, does NCrunch do something smart with workspace/cachefolder leftovers so it cleans them eventually even if I simply kill the process now and then?
If the process gets killed, the workspaces will be left behind, but they'll be automatically cleaned up by the next run. On initialisation, the engine always checks for orphaned workspaces and will automatically remove them.
Post a reply
Log in to reply.