[Buildbot-devel] status changes == source changes?

Brian Warner warner-buildbot at lothar.com
Sat Oct 14 20:53:20 UTC 2006

"A.T.Hofkamp" <a.t.hofkamp at tue.nl> writes:

> Wouldn't it be an alternative to view this output as yet another source of 
> changes, and then send messages between both parties, just like messages get 
> sent (and queue-ed) between source change, schedulers, and builders?
> We would then be able to collapse the status output infra structure and the 
> builder infra structure together into a single mechanism.
> Would this be a good idea?

I can't say that I understand what this would mean. The current architecture
can be viewed as a big set of connected queues[1], each delivering different
kinds of messages from one component to another. Status information messages
flow from the Builders and the Builds and the Steps to their associated
status objects (BuilderStatus, BuildStatus, BuildStepStatus respectively).
These status messages are pretty different than source-code Changes.. they
describe the results of a build, rather than the source code that went into a

So you need a different queue for Changes and status messages. They both use
roughly the same architecture, but have different subscribers. I'm afraid I
don't see how you might "unify" them any more than they currently are.


[1]: http://buildbot.sourceforge.net/manual-0.7.4.html#System-Architecture

More information about the devel mailing list