PowerShell task fails if there is any output to standard error (Bug #269)
The PowerShell task causes a build to fail if there is any output to standard error. Please update the PowerShell task to not do this. Just because an error occurs doesn't mean a build should fail. The executable task only uses exit codes to determine if a process fails. I think the PowerShell should do the same.
To be a little clearer, I believe this is a breaking change than earlier versions of CCNet (1.6, specifically). We have a lot of builds that run tests in PowerShell. Some of those tests write errors out, but it doesn't mean the tests fail, just that the code being tested is writing an error. With 1.8.3, these test builds fail even though there are no failing tests. Would it be possible to create a configuration option on the PowerShell task that will fail the build if anything any errors are written, something like:
The default value would be false, to preserve behavior with 1.6.
that change (breaking the build) was done for issue fixing #42
Adding a configuration option is an idea to keep each scenario :
anyone got a better name?
- Status changed from New to Feedback
- Assignee set to Ruben Willems