[Buildbot-devel] Buildbot 1.0: The Shimmering Vision

Neil Hemingway neil.hemingway at googlemail.com
Thu Aug 7 12:39:18 UTC 2008


Pretty much everything we need to do is reasonably easy with the current
version of bb.  Most of my tinkering has been around the edges
(notification, prioritization, etc).

Perhaps the only real difference we have is the _way_ we use it.  Most
installations seem to have a builder per architecture, but we don't need
that as we have only one architecture (we build a perl web app)  However, we
do like being able to see which branches are passing and which are not, so
we have a builder for releases, a builder for trunk and a builder per
branch.  This generates multiple columns in the waterfall giving us what we
want.  All the builders are currently identical (tho I'm planning to change
the release one to do some additional steps)

As such, we don't really need multiple builders, we just need to be able to
separate out builds by branch (which could probably be done some other way)

It might therefore be sensible to have the status tools (whatever replaces
waterfall, etc) be able to display builds in columns per $configurable_thing
(branch in our case, builder for most people) rather than just a column per
builder (reproducing what we have now, but without needing multiple
builders)

Just my 2p
Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20080807/2f5b55c1/attachment.html>


More information about the devel mailing list