0

I'm running a .bat file via the InvokeProcess activity in a build process template.

The file is well executed along within a queued build but the error log (to the console) of my .bat file is not visible in the Summary section of the executed build report.

How can we print our message into this section?

ps.

When I put error command in my .bat file, the build is just continued without any error text displayed. The build even results as succeeded.

Community
  • 1
  • 1
Nam G VU
  • 33,193
  • 69
  • 233
  • 372
  • 1
    The InvokeProcess activity looks at the output streams from the program it is running. I don't think you can force content from a batch file to write to stderr. Your best option is to write your output which will show up in the diagnostic log and then use exit /b %EXITCODE% to indicate the script completed with error. – Chris Patterson Dec 13 '13 at 13:25
  • @ChrisPatterson How can we write output into `diagnostic log`? – Nam G VU Dec 17 '13 at 08:48
  • All output from both stderr stdout goes into the diagnostic log. There is no way to make it go to the summary section. – Chris Patterson Jan 30 '14 at 21:28

0 Answers0