Hi, On Wed, Aug 21, 2013 at 12:38 PM, Aaron Meurer <[email protected]> wrote: > On Wed, Aug 21, 2013 at 1:21 PM, Matthew Brett <[email protected]> > wrote: >> Hi, >> >> On Wed, Aug 21, 2013 at 11:36 AM, Jason Moore <[email protected]> wrote: >>> Some docs on it: >>> http://docs.buildbot.net/latest/manual/cfg-statustargets.html#status-GitHubStatus >>> >>> Matthew, do you understand this? I'll need to get up to speed on buildbot >>> before I get it. >> >> Sort of. Buildbot has 'status targets' which accept the results of a >> build and send them somewhere. The ones I've currently got active >> are: >> >> * the default dynamic web server : e.g. http://nipy.bic.berkeley.edu/builders >> * email notifications - because y'all seemed to want that >> >> (see the last few lines of the configuration file : >> https://github.com/nipy/nibotmi/blob/master/master.cfg#L1257) >> >> This pull request seems to add a status target that uses the github >> API to update the github 'statuses' of particular commits. >> >> https://github.com/buildbot/buildbot/pull/635/files#L3R1580 >> http://developer.github.com/v3/repos/statuses/ >> >> I think you can have more than one status for a commit, but only the >> most recent is shown: >> >> https://github.com/blog/1227-commit-status-api > > So it's almost as bad as I thought. Is there any way at all to see > multiple statuses on a commit? I guess you have to use the API.
I guess so - so you might have to fall back to email notifications instead. Cheers, Matthew -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
