|
||||||||
|
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-15965) Currently ... [email protected] (JIRA)
- [JIRA] (JENKINS-15965) Curre... [email protected] (JIRA)
- [JIRA] (JENKINS-15965) Curre... [email protected] (JIRA)
- [JIRA] (JENKINS-15965) Curre... [email protected] (JIRA)
- [JIRA] (JENKINS-15965) Curre... [email protected] (JIRA)
- [JIRA] (JENKINS-15965) Curre... [email protected] (JIRA)
- [JIRA] (JENKINS-15965) Curre... [email protected] (JIRA)

Having done some searching on the issue of downstream upstream build numbers it looks like it could be difficult only using numbers. One(execution) build can be triggered by multiple upstream builds.
My suggestion is to hack in a build parameter ID that is generated unique for sub build. And then somehow match against this build parameter. But as I have already stated I do not know MultiJob and Jenkins internals at all.