Multiple SCMs Plugin doesn't track multiple Git Repo SHA1

XMLWordPrintable

      When we go to each build log, as in ...jenkins/job/<job name>/1, we have a list of Changes from Git which identifies the corresponding SHA1 against the changes. However, since Jenkins job configure only gives 1 GitHub project url, and we are using the Multiple Git plugin, the SHA1 attached always refer to the 1 repo, even though it might belong to a different repo.

      Example:

      repo1
      -change 1: SHA1=12345
      repo2
      -change 3: SHA1=09876

      The change list on that page shows

      Changes
      Git

      Changelog updated by ... (commit: 12345) (detail)
      Getting gitzip version (commit: 09876) (detail)

      When I click on the commit link, they both leads to repo1's commit history. The first link will work because the SHA1 belongs to repo1, the second link will fail

            Assignee:
            Kevin Bell
            Reporter:
            Tony Yang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: