Hi Jenkins Users,
We have a Jenkins (2.9) multi-branch pipeline project. It has 2 git source
repositories configured so that we pick up and list any branch named
"release/3.*". Now each of 2 git repos has a branch named release/3.1.0.
Jenkins detects both branches, but refuses to add the second one to the
list of branches because there is already an item with the same name. In
"scan multi-branch pipeline log" log, I see this message:
Checking branch release/3.1.0
‘Jenkinsfile’ found
Met criteria
Ignoring <2nd-repo-name> >> release/3.1.0 from source #2 as source #1 owns the
branch name
Is it possible to change this behavior? It could be done by instructing
Jenkins to use "<repository-name>-<branch-name>" schema in list item names.
Thanks for any help!
D.D.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/b9c8327e-561e-4dc8-8c01-02ca567a47cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
