Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47874

Support multiple repositories in multi-branch pipeline

    • 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

          Alastair D'Silva created issue -
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          Alastair D'Silva made changes -
          Attachment New: branchindexing.log [ 40255 ]
          Mark Waite made changes -
          Summary Original: Resolve branch names collisions New: Support multiple repositories in multi-branch pipeline
          Alastair D'Silva made changes -
          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
          Rok Povse made changes -
          Sprint New: Blue Ocean 1.5 - beta 3 [ 491 ]
          Rok Povse made changes -
          Assignee New: Andrew Bayer [ abayer ]
          Rajalakshmi Nagendran made changes -
          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.

           
          Andrew Bayer made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]

            Unassigned Unassigned
            evildeece Alastair D'Silva
            Votes:
            18 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: