You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I would like to achieve with it is to send the build results (e.g. why the build failed, as it can be seen under /viewLog) to HipChat directly, because would like to avoid the devs having to have credentials for more systems, TC in this case. As far as I can tell, it’s not possible at the moment.
I’m not sure if it’s feasible, but the build log/overview could be a useful addition to the currently available set of object variables as listed in one of your previous blogposts (http://netwolfuk.wordpress.com/2013/08/31/custom-templates-and-branches-in-tcwebhooks).
The text was updated successfully, but these errors were encountered:
You can probably use a custom parameter passed to webhooks for this, seems kind of roundabout though -- would be nice for a built-in parameter that shows the full build status, include failures like what we see on the status screen.
For example one of our recent builds failed with this reason under "compilation error":
EXEC Undefined variable: "$light-grey".
Would be awesome to include that in the message to Slack.
On a completed build the value of buildStatus gives you the same one line summary as is displayed by TeamCity on the home page. Would that work for you?
I'd still like to see more information. If I make a request against /app/rest/testOccurrents?locator=build:<id>,status:FAILURE I will get back specific information on the actual test the failed, not just the number.
What I would like to achieve with it is to send the build results (e.g. why the build failed, as it can be seen under /viewLog) to HipChat directly, because would like to avoid the devs having to have credentials for more systems, TC in this case. As far as I can tell, it’s not possible at the moment.
I’m not sure if it’s feasible, but the build log/overview could be a useful addition to the currently available set of object variables as listed in one of your previous blogposts (http://netwolfuk.wordpress.com/2013/08/31/custom-templates-and-branches-in-tcwebhooks).
The text was updated successfully, but these errors were encountered: