-
New Feature
-
Resolution: Unresolved
-
Major
-
Jenkins 2.88
Git Plugin 3.6.4
Branch API Plugin 2.0.15
Pipeline Multibranch 2.16
-
-
Blue Ocean 1.5 - beta 3
Within a single job, we need to source branches from multiple repositories that we do not have control over. Currently, if the same branch name occurs in different repositories, only the first is built and subsequent identical branches are dropped.
I suggest that the remote name (if configured) be used to disambiguate the branches, so that they can all be built.
eg.
Remote name: linux
Branch: master
Remote Name: linux-next
Branch: master11
These would be resolved as linux/master and linux-next/master.
[JENKINS-47874] Support multiple repositories in multi-branch pipeline
Assignee | Original: Mark Waite [ markewaite ] |
Attachment | New: branchindexing.log [ 40255 ] |
Summary | Original: Resolve branch names collisions | New: Support multiple repositories in multi-branch pipeline |
Component/s | New: branch-api-plugin [ 18621 ] | |
Component/s | New: workflow-multibranch-plugin [ 21465 ] | |
Component/s | Original: git-plugin [ 15543 ] | |
Environment |
Original:
Jenkins 2.88 Git Plugin 3.6.4 |
New:
Jenkins 2.88 Git Plugin 3.6.4 Branch API Plugin 2.0.15 Pipeline Multibranch 2.16 |
Sprint | New: Blue Ocean 1.5 - beta 3 [ 491 ] |
Assignee | New: Andrew Bayer [ abayer ] |
Description |
Original:
Within a single job, we need to source branches from multiple repositories that we do not have control over. Currently, if the same branch name occurs in different repositories, only the first is built and subsequent identical branches are dropped. I suggest that the remote name (if configured) be used to disambiguate the branches, so that they can all be built. eg. Remote name: linux Branch: master Remote Name: linux-next Branch: master These would be resolved as linux/master and linux-next/master. |
New:
Within a single job, we need to source branches from multiple repositories that we do not have control over. Currently, if the same branch name occurs in different repositories, only the first is built and subsequent identical branches are dropped. I suggest that the remote name (if configured) be used to disambiguate the branches, so that they can all be built. eg. Remote name: linux Branch: master Remote Name: linux-next Branch: master11 These would be resolved as linux/master and linux-next/master. |
Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Assignee | Original: Andrew Bayer [ abayer ] |