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

Support multiple repositories in multi-branch pipeline

    XMLWordPrintable

    Details

    • 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.

       

        Attachments

          Activity

          evildeece Alastair D'Silva created issue -
          markewaite Mark Waite made changes -
          Field Original Value New Value
          Assignee Mark Waite [ markewaite ]
          evildeece Alastair D'Silva made changes -
          Attachment branchindexing.log [ 40255 ]
          markewaite Mark Waite made changes -
          Summary Resolve branch names collisions Support multiple repositories in multi-branch pipeline
          evildeece Alastair D'Silva made changes -
          Component/s branch-api-plugin [ 18621 ]
          Component/s workflow-multibranch-plugin [ 21465 ]
          Component/s git-plugin [ 15543 ]
          Environment Jenkins 2.88
          Git Plugin 3.6.4
          Jenkins 2.88
          Git Plugin 3.6.4
          Branch API Plugin 2.0.15
          Pipeline Multibranch 2.16
          povserok Rok Povse made changes -
          Sprint Blue Ocean 1.5 - beta 3 [ 491 ]
          povserok Rok Povse made changes -
          Assignee Andrew Bayer [ abayer ]
          divyanagendran Rajalakshmi Nagendran made changes -
          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: master

          These would be resolved as linux/master and linux-next/master.

           
          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.

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

            People

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

              Dates

              Created:
              Updated: