A way to output "important" messages from Command Line build step

Hello,

I am running custom tests using command line. When tests fail, I see message like "[Step 2/3] Step failed" in "Overview" and "Build log > Important messages" panel. My test outputs some data to stdout, but it could only be seen when viewing all output messages

I wonder if there is a way to output data from command line build step so that some messages will be treated as "important".or "errors" and will be displayed accordingly?

Thanks

3 comments
Comment actions Permalink

All output written to stderr is treated as important. But probably there is a better solution for your case. You mentioned that you have custom test runner, but how you report tests to TeamCity?

0
Comment actions Permalink
All output written to stderr is treated as important.


Thanks, stderr output seems to be what I wanted.

. You mentioned that you have custom test runner, but how you report tests to TeamCity?


I just don't do that now (no TC integration for our test system) All tests are run as a command line build step that fails if any test fails. Test system outputs some messages to stdout to identify which test has failed.

It will be interesting to know if there is a  way to output test results from command line build step so that TeamCity would somehow parse them

0
Comment actions Permalink

There are at least two options:
- produce JUnit like xml reports
- use TeamCity service messages: http://confluence.jetbrains.net/display/TCD6/Build+Script+Interaction+with+TeamCity

0

Please sign in to leave a comment.