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

MultiScm configurations does not resolve corret git-client (our case 12426)

    Details

    • Similar Issues:

      Description

      _Initial job configuration_

      • Four repositories in MultiScm configuration - one svn, three git
      • Two git repositories in one MultiScm SCM configurations:
      • *repo1*, named so it becomes default named `repo1`
      • *repo2*, named so it becomes default named `repo2`
      • branch specifier `*ready/*`
      • Checkout to sub-directory: repo1s
      • Prune stale remote-tracking branches
      • Wipe out repository & force clone
      • One git repository in one MultiScm SCM configurations:
      • *repo3*, named: `repo3`
      • branch specifier `*ready/*`
      • Checkout to sub-directory: repo3
      • Prune stale remote-tracking branches
      • Wipe out repository & force clone
      • One SVN repository in one MultiScm SCM configuration:
      • svn-repo checkout path
      • pretested integration configuration:
      • `master`
      • `repo3`
      • Accummulated strategy

      _Observations_

      • Pushing a ready branch to `repo3`, but there is nothing to do reported with error `Nothing to do the reason is: The branch name (repo3/ready/dev_865487921) used by git, did not match a remote branch name. You might already have integrated the branch`

      The problem is in the findSCM method, that just always return the first found SCM.

        Attachments

          Activity

          bue Bue Petersen created issue -
          bue Bue Petersen made changes -
          Field Original Value New Value
          Summary When using MultiScm configuration, the order of repositories matter when resolving git-client to use When using MultiScm configuration, the order of repositories matter when resolving git-client to use (our case 12426
          bue Bue Petersen made changes -
          Summary When using MultiScm configuration, the order of repositories matter when resolving git-client to use (our case 12426 When using MultiScm configuration, the order of repositories matter when resolving git-client to use (our case 12426)
          bue Bue Petersen made changes -
          Summary When using MultiScm configuration, the order of repositories matter when resolving git-client to use (our case 12426) MultiScm configurations does not resolve corret git-client (our case 12426)
          bue Bue Petersen made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          bue Bue Petersen made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Assignee Praqma Support [ praqma ] Bue Petersen [ bue ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 159948 ] JNJira + In-Review [ 208284 ]

            People

            • Assignee:
              bue Bue Petersen
              Reporter:
              bue Bue Petersen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: