[JIRA] (JENKINS-56210) Analyze JaCoCo's xml report instead of exec-files

[szhemzhitski@gmail.com (JIRA)]

Sergey Zhemzhitsky created an issue

Jenkins / JENKINS-56210 Analyze JaCoCo's xml report instead of exec-files Issue Type: New Feature Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2019-02-20 06:36 Priority: Minor Reporter: Sergey Zhemzhitsky There are some benefits on using xml reports instead of exec-files no dependency of jacoco.jar needed, so reports will be always actual no matter what jacoco version created them (currently if reports created by newer version of jacoco do not take any effect because jacoco-plugin's dependency is older); xml report contains all the information needed not to lose in the functionality of the plugin; report contains class, package, method coverage and their name - everything that is necessary for the plugin to work; in case of xml report - this report can be generated by the build tool or even by the jacoco's cli giving user more flexibility in configuring his build pipeline xml reports from any other coverage tools (scoverage, cobertura, etc.) can be easily converted into jacoco's xml format and get all the benefits of this plugin Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[szhemzhitski@gmail.com (JIRA)]

Sergey Zhemzhitsky updated an issue

Jenkins / JENKINS-56210 Analyze JaCoCo's xml report instead of exec-files

Change By: Sergey Zhemzhitsky

There are some benefits on using xml reports instead of exec-files

# no dependency of jacoco.jar needed, so reports will be always actual no matter what jacoco version created them (currently if reports created by newer version of jacoco do not take any effect because jacoco-plugin's dependency is older); # xml report contains all the information needed not to lose in the functionality of the plugin; report contains class, package, method coverage and their name - everything that is necessary for the plugin to work; # in case of xml report - this report can be generated by the build tool or even by the jacoco's cli giving user more flexibility in configuring his build pipeline # xml reports from any other coverage tools (scoverage, cobertura, etc.) can be easily converted into jacoco's xml format and get all the benefits of this plugin

Add Comment

[szhemzhitski@gmail.com (JIRA)]

Sergey Zhemzhitsky updated an issue

Jenkins / JENKINS-56210 Analyze JaCoCo's xml report instead of exec-files Change By: Sergey Zhemzhitsky

There are some benefits on using xml reports instead of exec-files

# no dependency of jacoco.jar needed, so reports will be always actual no matter what jacoco version created them (currently reports created by newer version of jacoco do not take any effect because jacoco-plugin's dependency is older);

# xml report contains all the information needed not to lose in the functionality of the plugin; report contains class, package, method coverage and their name - everything that is necessary for the plugin to work; # in case of xml report - this report can be generated by the build tool or even by the jacoco's cli giving user more flexibility in configuring his build pipeline

# xml reports from any other coverage tools (scoverage, cobertura, etc.) can be easily converted into jacoco's xml format and get all the benefits of this plugin (reporting, dashboard views, etc.)

Add Comment

[dominik.stadler@gmx.at (JIRA)]

centic commented on JENKINS-56210

Re: Analyze JaCoCo's xml report instead of exec-files There has been some discussion on this before, but unfortunately nobody took the task of actually working on it so it will likely not happen until someone invest the necessary time to contribute and maintain such a feature (ideally as non-default option first to not break all existing installations).

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)