|
||||||||
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 |
- [JIRA] (JENKINS-15160) earliest git hash pa... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... h...@coverity.com (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... h...@coverity.com (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... h...@coverity.com (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... h...@coverity.com (JIRA)
Thanks. Will this also solve the problem that only the git commit from the earliest trigger in a multiply triggered downstream job gets processed? In my example above, commit 4c41 from #415 never gets built (until I manually kick the job).