[Buildbot-devel] required fields forcing a build

[Todd Cooper]

I forgot to mention, yes I will work on it.

I am interested in somehow your expressing your vision better as I don't see it, but I highly respect it.




>________________________________
>From: Todd Cooper <todd_cooper at yahoo.com>
>To: Dustin J. Mitchell <dustin at v.igoro.us>
>Cc: "buildbot-devel at lists.sourceforge.net" <buildbot-devel at lists.sourceforge.net>
>Sent: Sunday, September 4, 2011 6:12 AM
>Subject: Re: [Buildbot-devel] required fields forcing a build
>
>
>Sounds a bit elaborate.  I like kiss, keep it stupid simple. 
>
>I was think more just being felxible enough to make each parameter flexible.
>
>
>I do think the force build needs to be more flexible, but should not not be more with a template?
>
>
>I so see the need for multiple schedulers with artibrary slaves.  I even see a build forced on a particular slave.
>The way the GUI is now seems somewhat sufficient in that you click on the column head.
>
>
>
>
>
>
>>________________________________
>>From: Dustin J. Mitchell <dustin at v.igoro.us>
>>To: Todd Cooper <todd_cooper at yahoo.com>
>>Cc: "buildbot-devel at lists.sourceforge.net" <buildbot-devel at lists.sourceforge.net>
>>Sent: Saturday, September 3, 2011 2:37 PM
>>Subject: Re: [Buildbot-devel] required fields forcing a build
>>
>>On Tue, Aug 30, 2011 at 5:15 PM,
 Todd Cooper <todd_cooper at yahoo.com> wrote:
>>> I am willing to add the following feature, but before I do, I was wondering
>>> if anyone had an idea to do this with the way buildbot currently is.
>>>
>>> I want to be able to make some fields 'required' when forcing a build so
>>> that at least the name and reason is filled in.
>>> I am sure people have had this problem with people clicking buttons and not
>>> documenting what they are doing.
>>
>>The force-build web interface isn't very good right now.  OK, it's
>>downright terrible.
>>
>>In fact, I'd like to switch the whole thing out and replace it with a
>>scheduler that can be made to schedule builds based on input from the
>>web.  Such a scheduler should be sufficiently configurable to suit all
>>of the needs I've seen for force-build:
 it can schedule on
 an
>>arbitrary set of builders; it can require whatever
>>parameters/properties it would like; multiple schedulers, each with
>>their own page, could be defined to handle multiple forcing needs in
>>the same master; and it would have the advantage of removing the one
>>means of creating a buildset that does not come from a scheduler.
>>
>>Do you want to work that up?
>>
>>Dustin
>>
>>
>>
>------------------------------------------------------------------------------
>Special Offer -- Download ArcSight Logger for FREE!
>Finally, a world-class log management solution at an even better 
>price-free! And you'll get a free "Love Thy Logs" t-shirt when you
>download Logger. Secure your free ArcSight Logger TODAY!
>http://p.sf.net/sfu/arcsisghtdev2dev
>_______________________________________________
>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/20110904/28aabf6e/attachment.html>