Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: branch-api-plugin, workflow-multibranch-plugin
-
Labels:
-
Environment:Jenkins 2.88
Git Plugin 3.6.4
Branch API Plugin 2.0.15
Pipeline Multibranch 2.16
-
Similar Issues:
-
Sprint:Blue Ocean 1.5 - beta 3
Description
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.
I suspect that changes will be needed in multiple plugins to support your use case.
I don't think changes are needed in the git plugin, but I would expect changes would be needed in the branch api, and possibly in the branch source plugins and the organization folder plugin.