<p>The JUNIT plugin has a built-in publisher for aggregating test results called "Aggregate Downstream Test Results". You need to make sure that the 'parent' and 'child' jobs are linked together with a downstream/upstream relation. This is usually done by archiving an artifact in the parent build and copying it to the children builds using the 'Archive Artifact' publisher and the 'Copy Artifact' buildstep respectively. </p>

CC BY-SA 4.0
2018-09-12T16:18:12.547Z
Fair point. Edited for (some) clarity.
Myrrhman
CC BY-SA 4.0
2018-09-12T16:54:42.090Z
much better ...
Pierre.Vriens
CC BY-SA 4.0
2020-07-30T07:24:14.603Z
Hi there! Any chance to elaborate or give resources on how to achieve this? I'm trying hard to access the archived logs but I'm failing badly.
andreee
CC BY-SA 4.0
2018-09-12T16:04:59.990Z
2018-09-12T16:17:19.347Z
2018-09-12T16:17:19.347Z
Myrrhman
<p>If you are able to use gradle, maybe use something like mentioned here:</p>

<p><a href="https://github.com/codecov/example-gradle" rel="nofollow noreferrer">Multi-module projects</a>
or
<a href="https://csiebler.github.io/blog/2014/02/09/multi-project-code-coverage-using-gradle-and-jacoco" rel="nofollow noreferrer">this</a></p>

<p>Also you'll get coverage :)</p>

CC BY-SA 4.0
2018-07-18T19:26:04.597Z
2018-07-18T19:26:04.597Z
saikek
<p>We have a Jenkins setup which utilizes multiple projects for running various suites of tests for our application.</p>

<p>There is one 'parent' project, which is triggered by Git commits. This project in turn builds our 'child' project. Each child projects runs a series of defined tests.</p>

<p>Each project is setup with JUnit to output onto the build page the results of the tests.</p>

<p>In order to get a comprehensive view of commits across our entire project, you need to go to the build page of EACH of our 'child' projects to see the results.</p>

<p>What I would like to do is aggregate ALL the JUnit reports, from builds triggered by out 'parent' project across all the 'child' projects to one place so we can view all the test results together.</p>

<p>Does anyone have experience with something like this? </p>

<jenkins><jenkins-plugins>
Aggregating JUnit test results from multiple projects
ABD
# Aggregating JUnit test results from multiple projects

(Asked by: username_0 on 2018-07-18)

We have a Jenkins setup which utilizes multiple projects for running various suites of tests for our application.

There is one 'parent' project, which is triggered by Git commits. This project in turn builds our 'child' project. Each child projects runs a series of defined tests.

Each project is setup with JUnit to output onto the build page the results of the tests.

In order to get a comprehensive view of commits across our entire project, you need to go to the build page of EACH of our 'child' projects to see the results.

What I would like to do is aggregate ALL the JUnit reports, from builds triggered by out 'parent' project across all the 'child' projects to one place so we can view all the test results together.

Does anyone have experience with something like this?

**Tags:** jenkins, jenkins-plugins


---

## 2 answers

### Answer by username_1 on 2018-09-12. Score: 4

The JUNIT plugin has a built-in publisher for aggregating test results called "Aggregate Downstream Test Results". You need to make sure that the 'parent' and 'child' jobs are linked together with a downstream/upstream relation. This is usually done by archiving an artifact in the parent build and copying it to the children builds using the 'Archive Artifact' publisher and the 'Copy Artifact' buildstep respectively.

> **Comments:**
> **username_1**: Fair point. Edited for (some) clarity.  
> **username_2**: much better ...  
> **username_3**: Hi there! Any chance to elaborate or give resources on how to achieve this? I'm trying hard to access the archived logs but I'm failing badly.  

---

### Answer by username_4 on 2018-07-18. Score: -1

If you are able to use gradle, maybe use something like mentioned here:

[Multi-module projects](https://github.com/codecov/example-gradle)
or
[this](https://csiebler.github.io/blog/2014/02/09/multi-project-code-coverage-using-gradle-and-jacoco)

Also you'll get coverage :)


---

