Service messages get hidden by unit test results Follow

Just posting to bump this to the top. I'd really like to hear from JetBrains or anyone in the community if they have been able to get this to work.

Bumping this again. I would really appreciate a reply.

Hello,

  Looks like this is my area of responsibility. Next week, I'll take a look whether we could provide a simple fix, and if so,
  it will go to 4.5.1. If not, this will be fixed only in 5.0.

  Regards,
  KIR

Thanks. Looking forward to hearing a solution to this.

Hello Jonathon,

  Did you try using {build.status.text} pattern when setting build status text? Please read
  http://www.jetbrains.net/confluence/display/TCD4/Build%20Script%20Interaction%20with%20TeamCity#BuildScriptInteractionwithTeamCity-ReportingBuildStatus

  Kind regards,
  KIR

I am currently not using the buildStatus one to report the current progress. I am using the following 2 for the current progress and for a failure.

##teamcity[progressMessage '...message...']
##teamcity[buildStatus status='FAILURE' text='[...message...] {build.status.text}']

If I use the buildStatus message and set the status to SUCCESS after I have reported a failure will TeamCity switch back to being successful?

jonorossi wrote:

I am currently not using the buildStatus one to report the current progress. I am using the following 2 for the current progress and for a failure.

##teamcity[progressMessage '...message...']
##teamcity[buildStatus status='FAILURE' text='[...message...] {build.status.text}']

If I use the buildStatus message and set the status to SUCCESS after I have reported a failure will TeamCity switch back to being successful?

    I believe, you can omit 'status' attribute from the buildStatus message.

    Does it work for you?

The docs don't state it is optional, but I'll give it a try and let you know how I go.

Kirill,

Thanks heaps. That worked really well, it is exactly what I have been after. The nice thing is that the last build status you announce, TeamCity will leave on the dashboard after the build finishes.

You might like to get the docs updated because TeamCity is much more flexible in this area than the docs lead on.

Thanks again, Jono

You might like to get the docs updated because TeamCity is much more flexible in this area than the docs lead on.

Thanks again, Jono

    Thanks for suggestion, I've corrected the docs

    Regards,
    KIR