-
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.
Interesting, that is the behavior I was expecting, but not what I am seeing.
I'm using a Multibranch pipeline job, I've attached an excerpt from the scan log (branchindexing.log).
I have configured multiple git sources, each one has a unique "Configure Remote Name" value. Is there some other configuration option required to make the origin appear in the branch name?
Note the collision at the bottom of the log:
Checking branches...
Checking branch master
Met criteria
Ignoring Linux Kernel » master from source #5 as source #3 owns the branch name