Fail build if an stderr message is reported in the build log

Hi Andrew,

There are three message types in TC: error (red), warning (orange) and info (gray).  
std error stream corresponds to TeamCity warnings. It is impelented so because lots of messages are put in std error stream (for example timeout), which usually should not fail a build. So for command line only exit code not equals 0 corresponds to TeamCity error message. (For other type of runners there are more cases).
In your case you can:
1. Return non-zero exit code or set build status using service messages from script
2. Use something like this http://www.robvanderwoude.com/errorlevel.php (or bash -e)

I understand and have used service messages.  The problem in this case is the build is run by a lot of very large build scripts.  I do not want to change the scripts if possible.  I take it there's no way to cause the build to fail if a stderr message is reported?  If that is the case I may need to write a wrapper that catches the stderr stream and sets the exitcode appropriately if anything is caught, I was hoping to avoid this.

Now there is no other way to perform it. Please watch/vote for this issue http://youtrack.jetbrains.com/issue/TW-6994.

Quote from Hyung Cho on the issue you linked to:

Exit code doesn't really well describe the build errors.  STDERR does.  Because command line errors are treated like warnings, error strings are not displayed on Teamcity Build Overview page either.  Teamcity already has build failure option of "an error message is logged by build runner", but this option doesn't work for command line error message.
I believe Teamcity is treating Command Line runner error message as warning message is simply wrong.  Error message is NOT warnings.

I absolutely agree with this and have voted for the issue.  Thank you for getting back to me quickly.