[
https://issues.jenkins-ci.org/browse/JENKINS-13083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160268#comment-160268
]
Roland Schulz commented on JENKINS-13083:
-----------------------------------------
A possible partial solution to solve the problem in the core, is to identify
downstream builds without fingerprint. I filed a separate issue for that as
13084.
> Identify downstream matrix project with fingerprint
> ---------------------------------------------------
>
> Key: JENKINS-13083
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13083
> Project: Jenkins
> Issue Type: Improvement
> Components: matrix
> Reporter: Roland Schulz
>
> If a standard free-sytle downstream job is fingerprinting a file it is
> correctly identified as downstream build. But for a downstream matrix job
> this does not work. This is even though the fingerprinting works correctly as
> seen by fingerprint details. The fingerprint shows each of the configurations
> of the matrix job as a user of the file.
> This issue has been described before at
> http://jenkins.361315.n4.nabble.com/Question-about-Matrix-project-amp-fingerprints-amp-Join-plugin-td3857309.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
