Using artifact dependencies, can I merge code coverage data?


I have a build chain that involves concurrent unit-test and integration-test builds. Both of these generate code coverage data.

I am wondering if the build chain trigger that has them as dependencies can download and merge their coverage data? So then we can see the overall coverage of both unit and integration tests in the build chain parent, as well as the seperate coverages of the dependent builds.

1 comment
Comment actions Permalink

If both builds publish their coverage as artifacts then parent build can download these artifacts somehow merge and republish. For this parent build should use artifact dependencies and depend on the last finished builds, then artifacts will be taken from the build with the same sources.


Please sign in to leave a comment.