[Buildbot-devel] Buildbot Summit - Out of process

[Dustin J. Mitchell]

On Fri, Nov 26, 2010 at 9:37 PM, Marcus Lindblom <macke at yar.nu> wrote:
> Ah, so the current JSON is plagued by the same thing, and those details
> will change when we get DB-over-JSON. I got it.

Yes, but I'm assuming (hoping?) that these will be easier to adjust
than, say, the waterfall.

> Righto. So there will be some cold sweat anyhow to make this work in the
> future, and perhaps a JSON "DB-API" is the way forward. I hope it'll be
> able to do some SQL-like aggregated queries (I.e. get a bunch of builds
> or so, not just one at a a time... I'm not talking complex joins or
> selects here..)

Yep.  The plan is basically to expose an API that has methods folks
have found useful.  So no arbitrary query access, but for example a
method to pull rows from the various change-related tables together
into a single JSON response.

> Gimme a JSON/DB API and I'll maybe have a go at updating the WebStatus.
> It'd be interesting to see what kind of caching is necessary/doable to
> get a separate WebStatus up and running.
>
> Also, I can then write it in Django, just for fun ;-P

That would be awesome!  We will be using the current JsonStatus as a
starting point for the API design, although there may still be small
changes to that interface.  There will certainly be additional methods
added, too.  So if you wanted to spend a few minutes hacking against
that, that would be pretty cool.

Dustin