[Buildbot-devel] Feedback on message queuing design

Amber Yust ayust at yelp.com
Sun Oct 16 20:33:30 UTC 2011

I took a semi-casual look through it; from that perusal, it looks pretty


On Sun, Oct 16, 2011 at 1:23 PM, Dustin J. Mitchell <dustin at v.igoro.us>wrote:

> I've written up some documentation for a message-queuing design
> covering the data that's already in the database:
>  http://knuth.r.igoro.us/~dustin/buildbot-docs-mq/developer/mq.html
>  https://raw.github.com/djmitche/buildbot/mq/master/docs/developer/mq.rst
> I'd like to get some feedback - particularly from Amber and Tom, if
> you have time, but of course the more the merrier.
> There's more that will be included in 0.9.0, but I haven't fleshed it
> out yet.  Briefly: Build status will migrate to the database.  Most
> build information will be stored in a simple, flat form, but logs will
> be stored as "chunks" in a searchable format.  The JSON interface will
> be expanded to serve all data available in the database, with minimal
> translation of the current database API.  The JSON interface will also
> sport a means of consuming messages.  All of the code that's currently
> based on someobject.subscribeToSomeEvent will be converted to an mq
> consumer.  All of the code that currently implements IStatusReceiver
> will be converted to an mq consumer.
> Let me know what you think!
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20111016/5fc1696f/attachment.html>

More information about the devel mailing list