<br><br><div class="gmail_quote">On Sun, Oct 25, 2009 at 07:13, <span dir="ltr"><<a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On 12:48 pm, <a href="mailto:ctb@msu.edu" target="_blank">ctb@msu.edu</a> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
[snip]<div class="im"><br>
<br>
The most *exciting* part of pony-build, apart from the always-riveting<br>
spectacle of "titus rediscovering problems that buildbot solved 5 years ago",<br>
is the loose coupling of recording server to the build slaves and build<br>
reporters. My plan is to enable a simple and lightweight XML-RPC and/or<br>
REST-ish interface for querying the recording server from scripts or other Web<br>
sites. This has Brett aquiver with anticipation, I gather -- no more visual<br>
inspection of buildbot waterfall pages ;)<br>
</div></blockquote>
<br>
BuildBot has an XML-RPC interface. So Brett can probably do what he wants with BuildBot right now.<br></blockquote><div><br></div><div>Brett actually wants web hooks so pony-build will ping an App Engine web app when there is more data, ala PubSubHubbub. Or hell, just have pony-build have an Atom feed with updates and simply use PuSH. In other words I want to be told when there is an update, not have to poll to find out.</div>
<div><br></div><div>-Brett</div></div>