-
Improvement
-
Resolution: Unresolved
-
Major
-
None
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
- relates to
-
JENKINS-13084 Identify project triggered by other project as downstream project without fingerprinting
-
- Open
-
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.