On Fri, Apr 1, 2016 at 9:34 AM, Georges Racinet <[email protected]> wrote: >> Now for our own sake, I will separate from our actual build definitions in a >> git repo of its own, and see if I can make nice examples based on meta >> buidbot and SimpleConfig use-cases. > > So, here it is : https://github.com/anybox/anybox.buildbot.capability > > As it's been said before, it's a system to declare "capabilities" on > workers, and spawn automatically builders according to requirements or > multiplication (build_for) directives. This is "static" because this happens > at buildmaster startup or reconfiguration time. There's a full explanation > at http://docs.anybox.fr/anybox.buildbot.capability/master >... > Also, I've taken a look at contrib/SimpleConfig.py, but its examples don't > seem to be a good match to display the multiplication feature, because the > build variants are based on arbitrary tags, not on versions (there's an > example with workers having two Ubuntu versions, but no build uses both of > them if I got it right). Those examples could be rewritten using the > filtering requirements, but that actually makes it less simple.
We're using SimpleConfig.py; I recently ported it forward to 0.8.12. (Our master.json is 2748 lines :-) Its tags are not quite flexible enough, so I'm mulling improving it to meet our current use cases. If/when I do, maybe it'll be a better match for your capability system, I'll see if I can fit them together. (No promises about when :-( ) - Dan _______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
