On Fri, Mar 11, 2016 at 4:36 PM, Pierre Tardy <[email protected]> wrote:
> Hi Ed, > > Buildbot is the perfect fit for your usecase, and buildbot nine is an even > better fit (because the UI has great improvement on displaying trigger step) > That's brilliant. Thank you. I hadn't realised about version 9 (there doesn't seem to be a link to the 'latest' version from the 'current' version, though I may have missed it), but now that I know about it, I'll play with that one. > Indeed, your tricky part is #3, this can be performed via a trigger step, > as you said. > I would advise you to create one builder (say P) for all the variations, > and to parametrise it with properties. Then, you can use dynamic_trigger > create your builds, and choose how you mixup your properties/parameters for > each build > http://docs.buildbot.net/latest/manual/cfg-buildsteps.html#dynamic-trigger > I don't think I've entirely understood this yet, but I'm spending today working on it and I'm sure once I've had a go, it'll make more sense. > For step 4, just use the waitForFinish=True in the TriggerStep, and it > will wait for the result, and concatenate them so that the result of the > step is the worst result of all the triggered builds. > > If you attach your 10 slaves to the P builder, then buildbot will take > care of running all your parallel builds in those 10 slaves, when one > finish, it will take another from the queue. > > You can look at buildbot travis, which implement a dynamic trigger step > > https://github.com/tardyp/buildbot_travis/blob/master/buildbot_travis/steps/spawner.py > Thanks, this is exactly what I wanted. I'll have a good look through it. Ed
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
