[Buildbot-devel] Buildbot 1.0: The Shimmering Vision

[Ben Hearsum]

On 11-Aug-08, at 1:25 PM, John Earl wrote:

> Dustin J. Mitchell wrote:
>> The conflict I'm seeing here is between buildbot as a flexible,
>> general framework for continuous integration testing (capable of
>> supporting all of the weird uses we've seen in this thread so far)  
>> and
>> buildbot as a well-defined (and thus necessarily limited) application
>> which has knobs that can be spun via web.  The framework idea  
>> implies,
>> to me, that buildbot configurations are actually programs, which  
>> means
>> they aren't really editable (except via a <textarea>, I suppose) via
>> the web.
>>
>> The means I see for avoiding this conflict is to provide some tools
>> for building administrative interfaces, and ship a basic
>> trigger-these-builds-on-every-commit configuration which includes an
>> administrative interface.  Then folks who can get by with the basic
>> configuration get a web interface, and folks with more advanced
>> configuration needs can either roll their own administrative  
>> interface
>> or forgo it entirely.
>>
>
> We have one master and a *lot* of builders, so +1 on a nicer user
> interface for filtering information on builders or subsets of  
> builders.
> Even little things like letting builders be in more than one category
> would help.

you read my mind with regard to multiple categories. I guess that  
would turn them in to "tags" or "labels", but that's more useful, IMHO.