[users at bb.net] Specify different branches for different repos
jared.grubb at gmail.com
Fri Apr 8 07:04:15 UTC 2016
> On Apr 6, 2016, at 15:35, Riccardo Corsi <riccardo.corsi at kairos3d.it> wrote:
> Hi Jared,
> thanks for your reply.
> I've read some docs on the codebases but I still have some doubts:
> 1. is it mandatory to have a codebaseGenerator or can I simply specify a codebase dictionary as showed here in my force scheduler? http://docs.buildbot.net/0.8.12/manual/cfg-schedulers.html#codebaseparameter <http://docs.buildbot.net/0.8.12/manual/cfg-schedulers.html#codebaseparameter>
CodebaseParameter is what I use (I have 20 of them in each of my schedulers!)
> 2. in the source steps of my build, which parameters still need to be specified (repourl, branch, etc...) and which are read from the codebase?
> If one param (e.g. branch) is both present in the codebase and specified as source step property, which one will have the precedence?
Here’s what I use for each of my codebases, where “repo” is the defult repo URL:
The values passed from the Scheduler will override those here, if the scheduler specifies them.
> On Wed, Apr 6, 2016 at 5:02 AM, Jared Grubb <jared.grubb at gmail.com <mailto:jared.grubb at gmail.com>> wrote:
> 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.
>> On Apr 4, 2016, at 01:24, Riccardo Corsi <riccardo.corsi at kairos3d.it <mailto:riccardo.corsi at kairos3d.it>> 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:
>> 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,
>> users mailing list
>> users at buildbot.net <mailto:users at buildbot.net>
>> https://lists.buildbot.net/mailman/listinfo/users <https://lists.buildbot.net/mailman/listinfo/users>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users