[Buildbot-devel] Is there a build-god? Or any aggregated view for multiple build masters?

Marcus Lindblom macke at yar.nu
Sun Nov 7 12:04:33 UTC 2010


On 2010-11-06 23:19, Charles Lepple wrote:
> On Nov 5, 2010, at 9:58 AM, Dustin J. Mitchell wrote:
>
>> First, make the web status primarily a client-side application, which
>> merely requests status information from the master via JSONRPC.  Use
>> long polling or other mechanisms to get status updates, and do so in a
>> fashion that can poll multiple masters.
>
> When you say a "client-side application", are you referring to a
> static web page which uses JavaScript to request the current build/
> slave/whatever status?

I believe that's the new plan. I'm a bit sad to see my jinja setup go 
away, but OTOH a client-side html app is pretty neat too. :)

OT: I'd heartily recommend jQuery as a javascript lib.

>   From what little I understand about JSON, it sounds like a web page
> would have to use an XmlHttpRequest, and I think that the origination-
> server issue would limit you to aggregating multiple masters on the
> same host. (I was pondering this to provide a top-level indication of
> what is going on across several masters, each located on a different
> host.)

I think one can work around that by using JSONP, i.e. fetch a script tag 
that provides continous updates but never closing the connection.
(http://en.wikipedia.org/wiki/JSON#JSONP).

Or the more recent cross-site object sharing for newer browsers:
(http://hacks.mozilla.org/2009/07/cross-site-xmlhttprequest-with-cors/)
(http://www.w3.org/TR/access-control/)

Or, failing that, set up the master webserver with proxies to the other 
buildmasters.

Cheers,
/Marcus





More information about the devel mailing list