How TeamCity Detects 'Important Messages' in the Build Log

Hi!

In our TeamCity build, we're using a NAnt script that calls devenv.com via the ]]> task. We do it this way because otherwise, C++ builds would fail due to the MSBuild script transformation done by TeamCity.

This works fine, but of course, TeamCity no longer is able to figure out which messages in the Build Log are important, thus, our developers have to carefully scan the whole log for error messages if a build fails.

Is there a way to tell TeamCity that a message printed to stdout should be regarded as important?

Thanks,
-Markus-

2 comments
Comment actions Permalink

Hello,

For now NAnt runner will only parse output from csc, jsc, vbc processes.
(thus ranaming devenv.com to say csc.com should solve the issue, but, I
know this kind of hack)

Please submit issue to our tracker, I think we attach improved version
of dotNetPlugin to try.

BTW. What was the issue with msbuild? Does it reproduces if starting from
command line?

Thanks!
--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi!

In our TeamCity build, we're using a NAnt script that calls devenv.com
via the <exec /> task. We it this way because otherwise, C++ builds
would fail due to the MSBuild script transformation done by TeamCity.

This works fine, but of course, TeamCity no longer is able to figure
out which messages in the Build Log are important, thus, our
developers have to carefully scan the whole log for error messages if
a build fails.

Is there a way to tell TeamCity that a message printed to stdout
should be regarded as important?

Thanks,
-Markus-



0
Comment actions Permalink

I have created the issue for that problem, could you please watch/vote for it at
http://jetbrains.net/tracker/issue/TW-4907

Thanks!

0

Please sign in to leave a comment.