Repository navigation
Monitor updates to pr and post Jenkins CI progress #5
Description
Activity
@phillipj Looking at @jbergstroem's work for the build team in that linked issue above, I see he/they are using the Github Status API. That seems like a cool way to go... maybe incorporate that in to the work you have in pollTravis?
Yeah we should probably push to the github status API. That way, it also displays at the merge button and you don't need to find the latest comment.
Related
githubmodule API: http://mikedeboer.github.io/node-github/#statuses, looking into it.@williamkapke trying to use to status API sounds awesome! One step closer to mimic Travis completely 👯
- changed the title
[-]Monitor updates to pr and post CI progress[/-][+]Monitor updates to pr and post CI progress (Status API)[/+]on Apr 8, 2016 - changed the title
[-]Monitor updates to pr and post CI progress (Status API)[/-][+]Monitor updates to pr and post CI progress[/+]on Apr 8, 2016 moving the status api discussion to #14
- changed the title
[-]Monitor updates to pr and post CI progress[/-][+]Monitor updates to pr and post Jenkins CI progress[/+]on Apr 8, 2016 @jbergstroem how would we know when to start polling? Could Jenkins do a HTTP requestagainst the bot, notifying there's a PR build that just started? Or should the bot listen for PR comments matching "CI: http://ci.nodejs.org/*"?
I owe a few of you a post -- sorry for the delay. I'm a bit backlogged at the moment; will get back to you shortly.
Seems the
../api/jsonendpoint would be perfect for polling build status. E.g. for nodejs/node#6342: https://ci.nodejs.org/job/node-test-pull-request/2363/api/jsonLanded with #35
Background and further details here: nodejs/build#236
I'd be happy to chip in here.