Tuesday 15 June 2010

How to ignore output from executable with CruiseControl.Net build? -


I'm searching a little bit and replacing the utility named fart.exe (yes, fart, like find and replace text) Works very well as part of CC Build.

The problem is that while working, FART shows a small ASCII spinner made of pipe, dash, slash ... | There is no way to suppress this spinner, and CC thinks that these small symbols are error messages and the build fails. I have tried:

  • Adding those symbols to CC as a perfectXextode - the same result, apparently only work ints
  • A batch file with echo OFF Calling farting through - it still outputs to the spinner and causes the failure

Any other ideas?

  & lt; Exec & gt; & Lt; Execution & gt; C: \ fart.exe & lt; / Execution & gt; & Lt; BuildArgs & gt; Myfile.txt string1 string2 & lt; / BuildArgs & gt; & Lt; SuccessExitCodes & gt; 1.0 & lt; / SuccessExitCodes & gt; & Lt; / Executive & gt; I ran on this issue with a mess and a CI system i  

executable Instead of compiling again, I redirected the output to NULL.

First I determined that the spinner's production was on stderr. Then I added "2> NUL" to the command line, which is called Goose, and now it is not used as a spinner on the stator.

Is anyone else getting a pinal in the aromatic air scene with that last sentence?


No comments:

Post a Comment