[Buildbot-devel] Multi-buildsteps and output environments

[Ludovic Chabant]

On Wed, Apr 24, 2013 at 4:49 PM, Dan Kegel <dank at kegel.com> wrote:

>
> Do you also do non-forced builds of those configurations?
> If so, then you probably have one builder per configuration,
> and the user can just check the checkboxes for each builder
> rather than using a pulldown.
>

Well actually we have a matrix of (platform x configuration). We build for
5 different platforms, and have 4 different configurations. I'm using a
single builder to build the code, but I pass it some build properties to
specify the platform and configuration to actually build. I'm not sure if
it's a bad thing or not, but it sure keeps things simpler both in code and
on the WebStatus pages.

It would be easy to generate separate builders for the some of the matrix
(say one builder per platform, with the configuration passed as a property)
or for the whole matrix. I'm basically trying to understand the pros and
cons of each approach.


IMHO you want to use as little of buildbot's magic as possible.  Ideally,
> it should just fire off "standard" builds without knowing anything at all
> about the project.  The less Buildbot knows about the projects, the happier
> you'll be.  This is not because Buildbot is hard to configure (though
> it kinda is),
> but because it's better to use exactly the same logic for automated
> and manual builds.
>

Well that's the thing: for our daily work, we usually open a console with
that script to setup the environment and then go from there. Think of it as
like setting up a virtualenv shell and doing everything there. So the logic
would be very close to what we do manually if I could have builders with
step 1 being that script, and all the other steps being whatever I want to
do.

--
   l u d o .
   . 8 0 17 80
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130424/5c009793/attachment.html>