Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failure reason from build log available as webhook parameter. #4

Open
netwolfuk opened this issue Jan 24, 2015 · 5 comments
Open

Comments

@netwolfuk
Copy link
Member

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).

@StrangeWill
Copy link

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.

@netwolfuk
Copy link
Member Author

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?

@netwolfuk
Copy link
Member Author

@StrangeWill Could you try the new slack templates released today and see if the result field is what you're after?

@netwolfuk
Copy link
Member Author

See issue #13

@sdemura
Copy link

sdemura commented Nov 29, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants