Details
-
Improvement
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
Android Gradle project
Description
When running gradle createDebugCoverageReport on an Android Gradle project, the built-in JaCoCo support builds an HTML report and an XML report.
As far as I know it is not possible to use this with Jenkins CI at the moment, because the plug-in wants the .exec file.
The report XML file starts with the following lines (looks like a standard format?):
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!DOCTYPE report PUBLIC "-//JACOCO//DTD Report 1.0//EN" "report.dtd">
<report name="debug">
<sessioninfo id="unknownhost-a0d58b54" start="1415952183361" dump="1415952207146"/>
I would love to see support for this in the Jenkins CI JaCoCo plug-in.
Attachments
Issue Links
- depends on
-
JENKINS-28652 JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
-
- Closed
-
Activity
centic
added a comment - JENKINS-28652 will provide a way to parse the XML report instead of the binary exec file.
centic
added a comment - JENKINS-28652 will provide a way to parse the XML report instead of the binary exec file. 
Bill Bagdon
added a comment - still not seeing a way to directly use a generated XML report centic
added a comment - JENKINS-28652 was solved in a different way due to lack of dev-time, so unless someone with enough time and skill steps in, this likely won't be available anytime soon, sorry.
centic
added a comment - JENKINS-28652 was solved in a different way due to lack of dev-time, so unless someone with enough time and skill steps in, this likely won't be available anytime soon, sorry. 
Mark R
added a comment - Any progress with this? The incompatibility between the old and new jacoco exec files will require a transition period where old and new coverage results can be understood. One way to do this would be to consume XML in the Jenkins plugin.
Mark R
added a comment - Any progress with this? The incompatibility between the old and new jacoco exec files will require a transition period where old and new coverage results can be understood. One way to do this would be to consume XML in the Jenkins plugin. 
That is not really a solution, betterswc.
It does not make sense to parse the data again, if the report has already been generated.
As you can tell, several people on GitHub also have mentioned this to be something they would like to see.