[JIRA] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

14 views
Skip to first unread message

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:09:02 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite created an issue
 
Jenkins / Bug JENKINS-28652
JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Issue Type: Bug Bug
Assignee: Ognjen Bubalo
Attachments: support.zip
Components: jacoco-plugin
Created: 30/May/15 3:08 PM
Environment: Jenkins 1.609.1
JaCoCo plugin 1.0.19
Priority: Major Major
Reporter: Mark Waite

The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting. The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

  1. create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
  2. build the branch "8c512c4ed5529c9d506ec1251232d19553b296ea" that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
  3. build the branch "aa7e532a9fdd947abe131efc006c7119ed430a41" that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
  4. build the branch "" that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph

I've attached a "support.zip" file from the Cloudbees support plugin which shows the version information of the various components I am using
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

scm_issue_link@java.net (JIRA)

unread,
May 30, 2015, 11:18:01 AM5/30/15
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon commented on Bug JENKINS-28652
 
Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

Code changed in jenkins
User: Mark Waite
Path:
pom.xml
http://jenkins-ci.org/commit/git-client-plugin/31e556b29cd179b7233495bbcedfee4a0bc82e48
Log:
Revert "Update jacoco dependency to 0.7.5.201505241946"

JaCoCo 0.7.5 shows no lines covered when displayed by Jenkins JaCoCo
plugin 1.0.19. Since Jenkins JaCoCo plugin 1.0.19 is based on JaCoCo
0.7.4 rather than 0.7.5, that may be expected.

The JaCoCo report in target/site/jacoco/index.html appears correct and
complete for JaCoCo 0.7.5, but the missing presentation in Jenkins means
this update needs to wait until the JaCoCo plugin is updated to support
JaCoCo 0.7.5.

Submitted JENKINS-28652 documenting the JaCoCo plugin problem

This reverts commit aa7e532a9fdd947abe131efc006c7119ed430a41.

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:30:01 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 

Job definition I used to show the issue
Change By: Mark Waite
Attachment: JENKINS-28652-JaCoCo-0.7.5-displays-no-coverage.xml

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:31:02 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-28652
 
Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Job definition I used to show the issue  is attached as JENKINS-28652-JaCoCo-0.7.5-displays-no-coverage.xml

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:36:02 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
Change By: Mark Waite
Attachment: JENKINS-28652-screen-shot.png

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:37:02 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting.  The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

# create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
# build the branch "8c512c4ed5529c9d506ec1251232d19553b296ea" that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
# build the branch "aa7e532a9fdd947abe131efc006c7119ed430a41" that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
# build the branch " 31e556b29cd179b7233495bbcedfee4a0bc82e48 " that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph


I've attached a "support.zip" file from the Cloudbees support plugin which shows the version information of the various components I am using

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:41:03 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting.  The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

# create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
# build the branch " [https://github.com/jenkinsci/git-client-plugin/commit/ 8c512c4ed5529c9d506ec1251232d19553b296ea |8c512c4e] " that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
# build the branch " [https://github.com/jenkinsci/git-client-plugin/commit/ aa7e532a9fdd947abe131efc006c7119ed430a41 |aa7e532a] " that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
# build the branch " [https://github.com/jenkinsci/git-client-plugin/commit/ 31e556b29cd179b7233495bbcedfee4a0bc82e48 |31e556b2] " that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph

I've attached a " [^ support.zip ] " file from the Cloudbees support plugin which shows the version information of the various components I am using  and a [^JENKINS-28652-screen-shot.png|screen shot]

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:42:01 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting.  The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

# create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
# build the branch "[https://github.com/jenkinsci/git-client-plugin/commit/8c512c4ed5529c9d506ec1251232d19553b296ea |8c512c4e ]" that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
# build the branch "[https://github.com/jenkinsci/git-client-plugin/commit/aa7e532a9fdd947abe131efc006c7119ed430a41|aa7e532a]" that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
# build the branch "[https://github.com/jenkinsci/git-client-plugin/commit/31e556b29cd179b7233495bbcedfee4a0bc82e48|31e556b2]" that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph

I've attached a "[^support.zip]" file from the Cloudbees support plugin which shows the version information of the various components I am using and a [^JENKINS-28652-screen-shot.png|screen shot]

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:43:02 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting.  The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

# create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
# build the branch "[ 8c512c4e| https://github.com/jenkinsci/git-client-plugin/commit/8c512c4ed5529c9d506ec1251232d19553b296ea]" that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
# build the branch "[ aa7e532a| https://github.com/jenkinsci/git-client-plugin/commit/aa7e532a9fdd947abe131efc006c7119ed430a41 |aa7e532a ]" that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
# build the branch "[ 31e556b2| https://github.com/jenkinsci/git-client-plugin/commit/31e556b29cd179b7233495bbcedfee4a0bc82e48 |31e556b2 ]" that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph

I've attached a "[^support.zip]" file from the Cloudbees support plugin which shows the version information of the various components I am using and a [ screen shot| ^JENKINS-28652-screen-shot.png |screen shot ]

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 11:44:01 AM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting.  The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

# create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
# build the branch "[8c512c4e|https://github.com/jenkinsci/git-client-plugin/commit/8c512c4ed5529c9d506ec1251232d19553b296ea]" that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
# build the branch "[aa7e532a|https://github.com/jenkinsci/git-client-plugin/commit/aa7e532a9fdd947abe131efc006c7119ed430a41]" that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
# build the branch "[31e556b2|https://github.com/jenkinsci/git-client-plugin/commit/31e556b29cd179b7233495bbcedfee4a0bc82e48]" that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph

I've attached a "[^support.zip]" file from the Cloudbees support plugin which shows the version information of the various components I am using  and ,  a [screen shot|^JENKINS-28652-screen-shot.png] , and the [job definition|^JENKINS-28652-JaCoCo-0.7.5-displays-no-coverage.xml]

mark.earl.waite@gmail.com (JIRA)

unread,
May 30, 2015, 12:03:04 PM5/30/15
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
The JaCoCo maven plugin has released version 0.7.5.201505241946. I updated the Jenkins git-client-plugin from 0.7.4 to that new maven plugin for coverage reporting.  The summary graph and the source code tables all show no coverage (0%) even though the HTML coverage reports generated by JaCoCo show the correct values in target/site/jacoco/index.html.

Steps to show the problem:

# create a new Jenkins job which uses https://github.com/jenkinsci/git-client-plugin.git as its git repository with a Maven build step that performs "clean" and "install". Include a JaCoCo coverage report in the job definition using default settings
# build the branch "[8c512c4e|https://github.com/jenkinsci/git-client-plugin/commit/8c512c4ed5529c9d506ec1251232d19553b296ea]" that is the commit prior to the JaCoCo 0.7.5 change and confirm that the coverage report displays as expected
# build the branch "[aa7e532a|https://github.com/jenkinsci/git-client-plugin/commit/aa7e532a9fdd947abe131efc006c7119ed430a41]" that is the commit which switched to JaCoCo 0.7.5 and confirm that the coverage report displays 0% coverage. Confirm also in the repository that the target/site/jacoco/index.html file includes correct coverage reporting information
# build the branch "[31e556b2|https://github.com/jenkinsci/git-client-plugin/commit/31e556b29cd179b7233495bbcedfee4a0bc82e48]" that is the commit which reverted the swtich to JaCoCo 0.7.5 and confirm that Jenkins reporting is again showing the correct coverage summary graph

I've attached a "[^support.zip]" file from the Cloudbees support plugin which shows the version information of the various components I am using, a [screen shot|^JENKINS-28652-screen-shot.png], and the [job definition|^JENKINS-28652-JaCoCo-0.7.5-displays-no-coverage.xml] .

The jenkins.log file includes the following stack trace

{noformat}
May 30, 2015 7:44:40 AM hudson.model.Run execute
INFO: git-client-my-branches/master-update-jacoco-0.7.5 #1 main build action completed: SUCCESS
While reading execution data-file: /var/lib/jenkins/jobs/git-client-my-branches/branches/master-update-jacoco-0.7.5/builds/1/jacoco/execFiles/exec0/jacoco.exec
java.io.IOException: Incompatible version 1007.
        at org.jacoco.core.data.ExecutionDataReader.readHeader(ExecutionDataReader.java:127)
        at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:107)
        at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:87)
        at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:92)
        at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:132)
        at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102)
        at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:291)
        at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:273)
        at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:371)
        at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
        at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
        at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)
        at hudson.model.Build$BuildExecution.post2(Build.java:183)
        at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670)
        at hudson.model.Run.execute(Run.java:1766)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        at hudson.model.ResourceController.execute(ResourceController.java:98)
        at hudson.model.Executor.run(Executor.java:374)
{noformat}

dominik.stadler@gmx.at (JIRA)

unread,
Jul 22, 2015, 7:03:01 AM7/22/15
to jenkinsc...@googlegroups.com

clausfod@gmail.com (JIRA)

unread,
Oct 9, 2015, 1:47:02 AM10/9/15
to jenkinsc...@googlegroups.com
clausfod commented on Bug JENKINS-28652

Hi,

What's the status for closing this one ?

Kind regards
Claus Nielsen

dominik.stadler@gmx.at (JIRA)

unread,
Oct 12, 2015, 3:29:02 PM10/12/15
to jenkinsc...@googlegroups.com
centic commented on Bug JENKINS-28652

Unfortunately simply upgrading to JaCoCo 0.7.5 would break all installations still using 0.7.4, there was some discussion about switching to reading the data from the XML report in the plugin, but there seems to be a bit less information available there, so unless someone steps up to invest the time to implement this, it is unlikely to happen anytime soon, sorry.

dantran@gmail.com (JIRA)

unread,
Nov 1, 2015, 12:25:03 PM11/1/15
to jenkinsc...@googlegroups.com
dan tran commented on Bug JENKINS-28652

jacoco version using 0.x, this means this sort of compatibility breakage is expected

dominik.stadler@gmx.at (JIRA)

unread,
Nov 22, 2015, 6:34:05 PM11/22/15
to jenkinsc...@googlegroups.com
centic resolved as Fixed
 

Fixed by JaCoCo-Plugin 2.0.0 by simply forcing projects to upgrade to 0.7.5 as no-one could come up with the necessary changes to support both versions in parallel or switch to an XML-based report.
Change By: centic
Status: Open Resolved
Assignee: Ognjen Bubalo centic
Resolution: Fixed

mark.earl.waite@gmail.com (JIRA)

unread,
Nov 25, 2015, 9:45:05 PM11/25/15
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Fixed
 

Verified closed with plugin version 2.0.0
Change By: Mark Waite
Status: Resolved Closed

testingkaro@gmail.com (JIRA)

unread,
Feb 2, 2016, 1:47:03 PM2/2/16
to jenkinsc...@googlegroups.com
Maninder Singh reopened an issue
 

I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle
Can someone please help me. I have to downgrade the plugin for now.

Change By: Maninder Singh
Resolution: Fixed
Status: Closed Reopened

testingkaro@gmail.com (JIRA)

unread,
Feb 2, 2016, 1:59:05 PM2/2/16
to jenkinsc...@googlegroups.com
I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle  
  Using Jenkins 1.628
Can someone please help me. I have to downgrade the plugin for now.     

testingkaro@gmail.com (JIRA)

unread,
Feb 2, 2016, 2:07:02 PM2/2/16
to jenkinsc...@googlegroups.com
Maninder Singh edited a comment on Bug JENKINS-28652
I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle  Using Jenkins 1.628 . Surprised that I dit not have a problem with build.gradle using "0.7.5.201505241946" with Jenkins Plugin 1.0.19
Can someone please help me. I have to downgrade  the  my machine to  plugin  1.0.19  for now.     Which is working totally fine.

anandparajuli@gmail.com (JIRA)

unread,
Feb 23, 2016, 10:56:03 PM2/23/16
to jenkinsc...@googlegroups.com
AN2D commented on Bug JENKINS-28652

Current Jenkins version: 1.648
Jacoco plugin version: 2.0.1
OS - Windows 7

Jacoco plugin shows 0% for all projects. Logs below.

This was working fine in our previous Jenkins instance in Linux which was using Jacoco plugin 1.0.19.

[JaCoCo plugin] Collecting JaCoCo coverage data...
[JaCoCo plugin] Project\build\instrumented\jacoco.exec;Project\build\instrumented\classes;Project\au\com; locations are configured
[JaCoCo plugin] Number of found exec files for pattern Project\build\instrumented\jacoco.exec: 1
[JaCoCo plugin] Saving matched execfiles:  C:\Program Files (x86)\Jenkins\workspace\Project\Project\build\instrumented\jacoco.exec
[JaCoCo plugin] Saving matched class directories for class-pattern: Project\build\instrumented\classes:  C:\Program Files (x86)\Jenkins\workspace\Project\Project\build\instrumented\classes
[JaCoCo plugin] Saving matched source directories for source-pattern: Project\au\com:  C:\Program Files (x86)\Jenkins\workspace\Project\Project\au\com
[JaCoCo plugin] Loading inclusions files..
[JaCoCo plugin] inclusions: []
[JaCoCo plugin] exclusions: []
[JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0]
[JaCoCo plugin] Publishing the results..
[JaCoCo plugin] Loading packages..
[JaCoCo plugin] Done.
[JaCoCo plugin] Overall coverage: class: 0, method: 0, line: 0, branch: 0, instruction: 0

lopez.sam@gmail.com (JIRA)

unread,
Feb 29, 2016, 5:26:05 PM2/29/16
to jenkinsc...@googlegroups.com

Seeing similar issue here:

Jacoco: 2.0.0
Jenkins: 1.642.1
OS: Ubuntu 14.04

While reading execution data-file: /jenkins/job/105/jacoco/execFiles/exec6/jacoco.exec
java.io.IOException: Incompatible version 1006.


at org.jacoco.core.data.ExecutionDataReader.readHeader(ExecutionDataReader.java:127)
at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:107)
at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:87)
at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:92)
at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:132)
at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102)

at hudson.plugins.jacoco.JacocoBuildAction.getResult(JacocoBuildAction.java:227)
at hudson.plugins.jacoco.JacocoBuildAction.getCoverageRatios(JacocoBuildAction.java:247)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)

dominik.stadler@gmx.at (JIRA)

unread,
Mar 1, 2016, 1:48:03 AM3/1/16
to jenkinsc...@googlegroups.com
centic commented on Bug JENKINS-28652

This indicates that you are still using JaCoCo 0.7 4 or earlier, the plugin version 2.0.0 requires 0.7.5 or newer to work.

anandparajuli@gmail.com (JIRA)

unread,
Mar 3, 2016, 5:06:03 PM3/3/16
to jenkinsc...@googlegroups.com
AN2D commented on Bug JENKINS-28652

Confirmed that Jacoco plugin version: 2.0.1 worked with the 0.7.6 version of jacocoagent.jar & jacocoant.jar. Thanks centic

dominik.stadler@gmx.at (JIRA)

unread,
Mar 4, 2016, 1:43:05 AM3/4/16
to jenkinsc...@googlegroups.com
centic resolved as Fixed
 

Setting to resolved based on latest comments, if you still see this, make sure you use JaCoCo >= 0.7.5 in your project and JaCoCo plugin >= 2.0.1 and if that still does not work, please create a new issue as it is likely not related to this problem.
Change By: centic
Status: Reopened Resolved
Resolution: Fixed

lopez.sam@gmail.com (JIRA)

unread,
Mar 4, 2016, 12:24:04 PM3/4/16
to jenkinsc...@googlegroups.com
Samuel Lopez commented on Bug JENKINS-28652
 
Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

Thanks,
On my side it looks like using the Mvn plugin at 0.7.5 fixes my issue

mark.earl.waite@gmail.com (JIRA)

unread,
Mar 15, 2016, 10:42:06 AM3/15/16
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Fixed
Change By: Mark Waite
Status: Resolved Closed

bhalachandra.g.bhat@gmail.com (JIRA)

unread,
Jun 7, 2016, 8:23:03 AM6/7/16
to jenkinsc...@googlegroups.com
bhalachandra bhat commented on Bug JENKINS-28652
 
Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

I am also facing the same issue and i am not able to fix that

bhalachandra.g.bhat@gmail.com (JIRA)

unread,
Jun 7, 2016, 8:27:05 AM6/7/16
to jenkinsc...@googlegroups.com

[JaCoCo plugin] Collecting JaCoCo coverage data...
[JaCoCo plugin] */.ec;/app/build/intermediates/classes/debug/com/calci/com/calculator1;*/app/src/main/java; locations are configured
[JaCoCo plugin] Number of found exec files for pattern */*.ec: 1
[JaCoCo plugin] Saving matched execfiles: C:\Users\310247986\AndroidStudioProjects\Calculator1\app\build\outputs\code-coverage\connected\coverage.ec
[JaCoCo plugin] Saving matched class directories for class-pattern: **/app/build/intermediates/classes/debug/com/calci/com/calculator1: C:\Users\310247986\AndroidStudioProjects\Calculator1\app\build\intermediates\classes\debug\com\calci\com\calculator1
[JaCoCo plugin] Saving matched source directories for source-pattern: **/app/src/main/java: C:\Users\310247986\AndroidStudioProjects\Calculator1\app\src\main\java


[JaCoCo plugin] Loading inclusions files..

[JaCoCo plugin] inclusions: [**/*.class]


[JaCoCo plugin] exclusions: []
[JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0]
[JaCoCo plugin] Publishing the results..
[JaCoCo plugin] Loading packages..
[JaCoCo plugin] Done.
[JaCoCo plugin] Overall coverage: class: 0, method: 0, line: 0, branch: 0, instruction: 0

Finished: SUCCESS

in my case .ec file is generated but it is showing 0% code coverage though XML file shows 17% of code coverage

kumar.manish087@gmail.com (JIRA)

unread,
Aug 29, 2019, 9:31:04 AM8/29/19
to jenkinsc...@googlegroups.com
Manish Kumar updated an issue
 
Change By: Manish Kumar
Attachment: Screenshot 2019-08-29 at 6.59.03 PM.png
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

kumar.manish087@gmail.com (JIRA)

unread,
Aug 29, 2019, 9:33:03 AM8/29/19
to jenkinsc...@googlegroups.com

I am also facing the same issue and i am not able to fix that. Covrage is showing 0 but  file in this location`java/target/site/jacoco/index.html` i am getting some number 


 
[JaCoCo plugin] Collecting JaCoCo coverage data...

[JaCoCo plugin] */SellerServicecode/java/target/jacoco.exec;/SellerServicecode/java/target/classes/com/myntra/seller/manager;*/SellerServicecode/java/src/main/java/com/myntra/seller/manager; locations are configured
[JaCoCo plugin] Number of found exec files for pattern **/SellerServicecode/java/target/jacoco.exec: 1
[JaCoCo plugin] Saving matched execfiles: /var/lib/jenkins/workspace/sellerService_Cov/SellerServicecode/java/target/jacoco.exec
[JaCoCo plugin] Saving matched class directories for class-pattern: **/SellerServicecode/java/target/classes/com/myntra/seller/manager:
[JaCoCo plugin] - /var/lib/jenkins/workspace/sellerService_Cov/SellerServicecode/java/target/classes/com/myntra/seller/manager 33 files
[JaCoCo plugin] Saving matched source directories for source-pattern: **/SellerServicecode/java/src/main/java/com/myntra/seller/manager:
[JaCoCo plugin] - /var/lib/jenkins/workspace/sellerService_Cov/SellerServicecode/java/src/main/java/com/myntra/seller/manager 30 files


[JaCoCo plugin] Loading inclusions files..

[JaCoCo plugin] inclusions: []


[JaCoCo plugin] exclusions: []
[JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0]
[JaCoCo plugin] Publishing the results..
[JaCoCo plugin] Loading packages..
[JaCoCo plugin] Done.
[JaCoCo plugin] Overall coverage: class: 0, method: 0, line: 0, branch: 0, instruction: 0

Finished: UNSTABLE
 

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 29, 2019, 9:48:05 AM8/29/19
to jenkinsc...@googlegroups.com

Manish Kumar questions posted to closed bug reports are seen by very few people. It is much better to ask questions in the Jenkins users mailing list or one of the Jenkins chat channels.

If you have a series of steps which another person can use to duplicate the problem, then you can open a bug report. Code coverage reporting as described in this bug report is working for me on my Jenkins installations in multiple projects.
Reply all
Reply to author
Forward
0 new messages