search

CodePadawans / ataru

MIT License
37 stars 3 forks source link

Exit status and stdout / stderr problems #81

Open troessner opened 9 years ago

troessner commented 9 years ago

We'd love to integrate ataru into our CI process but we're kind of blocked from doing this because of two reasons:

1.) ataru does not set any exit status depending on what the check actually resulted in. Meaning that this

 echo $?
0

will always be the same. Which makes it not suitable for CI integration since there's no automated way of knowing when the checks failed.

2.) When something goes wrong, e.g. a syntax error in the source code ataru still prints on STDOUT. Not on STDERR. So there is no way of telling the difference between output that one can ignore and legitimate failures.

Am I missing something here or is [1] and [2] something we just have to live with?

P.S.: Discussion started initally here: https://github.com/troessner/reek/pull/540

troessner commented 9 years ago

Update: [1] was my bad because of the way we shelled out to ataru in the rake task, please ignore that. I'd still be interested in [2] though..;)