{"action":"closed","issue":{"url":"https://api.github.com/repos/jonnyzzz/TeamCity.GitHub/issues/88","labels_url":"https://api.github.com/repos/jonnyzzz/TeamCity.GitHub/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/jonnyzzz/TeamCity.GitHub/issues/88/comments","events_url":"https://api.github.com/repos/jonnyzzz/TeamCity.GitHub/issues/88/events","html_url":"https://github.com/jonnyzzz/TeamCity.GitHub/issues/88","id":97716150,"number":88,"title":"Multiple build statuses for the same commit overwrite one another","user":{"login":"mattgibson","id":503900,"avatar_url":"https://avatars.githubusercontent.com/u/503900?v=3","gravatar_id":"","url":"https://api.github.com/users/mattgibson","html_url":"https://github.com/mattgibson","followers_url":"https://api.github.com/users/mattgibson/followers","following_url":"https://api.github.com/users/mattgibson/following{/other_user}","gists_url":"https://api.github.com/users/mattgibson/gists{/gist_id}","starred_url":"https://api.github.com/users/mattgibson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattgibson/subscriptions","organizations_url":"https://api.github.com/users/mattgibson/orgs","repos_url":"https://api.github.com/users/mattgibson/repos","events_url":"https://api.github.com/users/mattgibson/events{/privacy}","received_events_url":"https://api.github.com/users/mattgibson/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-07-28T14:09:38Z","updated_at":"2015-07-28T14:26:05Z","closed_at":"2015-07-28T14:26:05Z","body":"I have set up some build configurations where a plugin I have written is tested agains several different configurations of its host system. This results in several commit status updates to Github. However, if one of the earlier statuses is a fail and one of the later statuses is a pass, then the pass overwrites the fail and the pull request looks OK, even though it should not. \r\n\r\nI think the solution is to vary the context string that is sent with the status update. I think this is the same all the time at the moment, so if it was changed to include the build configuration id, then hopefully, the statuses would be separate, as in the case of other systems reporting to pull request separately (e.g. here: https://github.com/resque/resque-web/pull/93 - click on 'view details' next to the merge commit message to see that there are multiple status updates)\r\n\r\nBy using the build configuration id, a build that errored due to a config problem can be repeated and will correctly overwrite the mistake, but a different configuration for a different host system will not.\r\n\r\nMy Java skills are non-existent, so I'm not really in a position to make a pull request. Sorry!"}}