search

jonnyzzz / TeamCity.GitHub

Integration of TeamCity and GitHub
216 stars 63 forks source link

Customize context parameter to include build name #89

Open amir-arad opened 9 years ago

amir-arad commented 9 years ago

It is now possible to display results of multiple CI builds and systems by using different values in the context field of the report.

https://github.com/blog/1935-see-results-from-all-pull-request-status-checks

This will greatly improve visibility of branch / PR status if more than one job is concerned.

griwes commented 9 years ago

... #86, #87, #88 ...

sihil commented 9 years ago

Yes - it would make a lot of sense for the default to be the name of the TeamCity build, which is pretty much what I'm laboriously writing in to the content field by hand.

thevery commented 8 years ago

Is it possible to set branch name as context parameter (at least manually - as some build property)? Tried %build.branch% and a bunch of other parameters, but without any success, unfortunately (we're using build specs but getting %teamcity.build.branch%==<default>).

thevery commented 8 years ago

@iOSCowboy can you help me please with problem above as the author of context support feature?

thevery commented 8 years ago

Aaah, fixed via configuration instead of system/env parameter.

jonathanadler commented 6 years ago

@thevery I know this is old, but do you perhaps remember what exactly you did to fix this?

thevery commented 6 years ago

AFAIR instead of 2 status reports like 'feature_branch' and 'pull_request_number/merge' I've switched to 2 build configs from template, BUT better solution is to use built-in commit status publisher plugin which resolves this issue out of the box.