Your “all” builder needs to have two “codebases”, which is the term for each repo you want to manage. In other words, for each of A and B, you’d have the full set of repo/branch/revision/got_revision parameters.
Jared > On Apr 4, 2016, at 01:24, Riccardo Corsi <[email protected]> wrote: > > Hi Everyone, > > I have the following scenario, using buildbot 0.8.12: > project A with its own builder A and project B with builder B. > The 2 projects are based on 2 different git repos. > > Now i have a "builder All" which simply triggers builder A and B through > respective trigger schedulers, but I want to be able to specify 2 on the web > ui 2 different git branches to be used for A and B. > I have added a custom parameter "branch_for_b" which I then read as property > in the builderB's git step like this: > buildFactory.addStep(steps.Git( > branch = util.Property('branch_for_b', default='develop') > ...) > > But when I specify another branch in the standard branch field of the web ui > (which I intended for project A) it overrides whatever I set in branch_for_b, > as if B git's step is ignoring the property I'm passing and reading from the > "main" branch field. > > How am I supposed to handle this case? > Thank you, > Ricky > _______________________________________________ > users mailing list > [email protected] > https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
