OK, I think I see where the confusion is stemming from. What's going on is that the FingerprintAction, which holds the fingerprints that are returned by build.getBuildFingerprints() is associated with the matrix build (aka, the matrix parent), but the information in individual fingerprint records refer to the matrix child runs.
So if you want to figure out what fingerprints are used by the top level matrix build, you need to go through the usages of the fingerprints, and record each fingerprint that is used by the matrix child runs of that parent. -- Dean On 5/18/13 4:55 PM, "Chris Withers" <[email protected]> wrote: >On 17/05/2013 21:50, Dean Yu wrote: >>>> However, if I do the following on the job that created the artifacts >>>> used by the matrix build: >>>> >>>> build = job.getLastBuild() >>>> for (fp in build.getFingerPrints()) { >>>> println fg.getUsages(); >>>> } >>>> >>>> ...I do see the matrix children that used the artifact. >> >> I suspect that you are doing getFingerprints on the matrix parent job. > >Hmm, interesting, what's the "correct" test to use to see if I have a >matrix parent build? > >Chris > >-- >Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
