Then for all the jobs that produce or use these build artifacts, you
open the configuration and check the box "Record fingerprints of ..."
and enter the file names.
E.g. you have a build that produces a library called libA. You would
configure it to record fingerprint for the file libA.
You have another build which gets libA from the build artifacts of the
above job. You could e.g. use the Copy Artifacts plugin to get it.
Then you configure the job to record fingerprint for the file libA.
Jenkins sees the same checksum in those two builds of those two jobs
and now it knows they have a dependency. The dependency is used in
test result aggregation.
-- Sami
2012/4/7 lewis john mcgibbney <lewis.m...@gmail.com>: