Jenkins MultiJob Plugin does not aggregate downstream test results

9
votes

I am using the jenkins multijob plugin to execute a number of parallel builds in the same build phase and i want to display the test results in the main multijob project so i select a post-build action step to 'Aggregate down stream test results' and select both options 'Automatically aggregate all downstream tests' and 'Include failed builds in results' but when the jobs complete and i go into the main multijob project it shows 'no tests' under 'Latest Test Result' link...

Has anyone else encountered this issue? My downstream 'child' projects that run in parallel are multi-configuration projects.

1
jenkinsjenkins-plugins
I'm trying to do the exact same thing. Are you seeing Fingerprinting not enabled on this build. Test aggregation requires fingerprinting. when you click the Aggregated Test Result link on your builds? I've tried turning Fingerprinting on for both the downstream job and multi-job with no luck. - johnmcase
Looks like this is an open issue: https://issues.jenkins-ci.org/browse/JENKINS-18768 - johnmcase

1 Answers

12
votes

As a previous poster indicated, this is an open issue in the Jenkins JIRA and does not work. There is a workaround to achieve what your looking for. Your going to need the Copy Artifact Plugin and to also Archive the test result files as Artifacts in your jobs that are doing the test runs.

After you have installed this and configured your test run jobs properly, go to your Multijob and after all your test phases add a build step "Copy artifacts from another project" for each of the jobs you want the test results from. You can use "Specified by permalink" and use the "Last build" permalink to always retrieve the latest artifacts. Select the artifacts you want to copy (i.e. *.xml), and input your target directory as something like "job1". If you add multiple build steps to copy artifacts from another project, just name your target directories for the copied artifacts something similar like "job2", "job3", etc.

Then select a Post-build action in your Multijob as you would to Publish JUnit test result report (or whatever you prefer) and input **/job*/*.xml (or similar).

This is what I did, and it works just fine. It is a bit manual in the setup, but it works great once its configured.