Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13083

Identify downstream matrix project with fingerprint

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • matrix-project-plugin
    • 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

          [JENKINS-13083] Identify downstream matrix project with fingerprint

          Roland Schulz added a comment -

          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.

          Roland Schulz added a comment - 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.

            Unassigned Unassigned
            rschulz Roland Schulz
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: