![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Kevin Bell
|
|
Components:
|
multiple-scms |
|
Created:
|
13/Oct/14 7:24 PM
|
|
Description:
|
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
|
|
Environment:
|
LTS 1.565.3
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tony Yang
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
