Specify secondary repository at build plan branch level instead of build plan level

• Build project setup:
  • I have two different git repositories that I check out to create my build, one is the main project (default repository), the other is like dependencies but not compiled as this is PHP and as such not available as libraries that I could build separately.
  • To cater for that I use two repositories in the plan, both are defined on the master branch as default.
  • The first task of the build job is to checkout the code, the default first (my main project) then the additional repository in a sub directory of the checked out main project.
  • The rest of the build is straight forward, just zip the code, tag it and upload it to nexus.
• The Happy Path:
  • If I want to build master on both repository it's all good master is checked out on both repositories, it's all good
  • If I want to build a specific branch on the main repository and the master on the secondary ** repository, it's all good as well
• The Unhappy Path:
  • If I want to build a specific branch on the main repository and a specific branch (either matching the main one or not) on the secondary repository that's when things start to go wrong. I tried a number of configurations:
    • Specify the bamboo.planRepository.2.branchName variable in the branch settings but it seems to be set after the code is checked out.
    • Specify the bamboo.planRepository.2.branch variable in the branch settings but it seems to be set after the code is checked out.
    • Specify the bamboo.planRepository.2.branch.name variable in the branch settings but it seems to be set after the code is checked out.

None of that worked, although the variable are set the specified value it seems to happen after the checkout task rendering the setting of the variables kind of useless.

Thanks for your feedback.