[JENKINS-28652] JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary - Jenkins Jira

Mark Waite created issue - 2015-05-30 15:08

SCM/JIRA link daemon added a comment - 2015-05-30 15:17

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.

SCM/JIRA link daemon added a comment - 2015-05-30 15:17 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 Waite added a comment - 2015-05-30 15:29 - edited

Job definition I used to show the issue is attached as ~~JENKINS-28652~~-JaCoCo-0.7.5-displays-no-coverage.xml

Mark Waite added a comment - 2015-05-30 15:29 - edited Job definition I used to show the issue is attached as JENKINS-28652 -JaCoCo-0.7.5-displays-no-coverage.xml

Mark Waite made changes - 2015-05-30 15:29

Field	Original Value	New Value
Attachment		JENKINS-28652-JaCoCo-0.7.5-displays-no-coverage.xml [ 29870 ]

Mark Waite made changes - 2015-05-30 15:35

Attachment

JENKINS-28652-screen-shot.png [ 29871 ]

Mark Waite made changes - 2015-05-30 15:36

Description

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 "" 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

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 Waite made changes - 2015-05-30 15:40

Description

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

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 Waite made changes - 2015-05-30 15:41

Description

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]

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]" 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 Waite made changes - 2015-05-30 15:42

Description

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]" 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]

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]

Mark Waite made changes - 2015-05-30 15:43

Description

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]

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]

Mark Waite made changes - 2015-05-30 16:02

Description

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 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}

centic added a comment - 2015-07-22 11:02

PR https://github.com/jenkinsci/jacoco-plugin/pull/55 is also blocked by this.

centic added a comment - 2015-07-22 11:02 PR https://github.com/jenkinsci/jacoco-plugin/pull/55 is also blocked by this.

centic made changes - 2015-07-22 11:03

Link

This issue is blocking JENKINS-25616 [ JENKINS-25616 ]

clausfod added a comment - 2015-10-09 05:46

Hi,

What's the status for closing this one ?

Kind regards
Claus Nielsen

clausfod added a comment - 2015-10-09 05:46 Hi, What's the status for closing this one ? Kind regards Claus Nielsen

centic added a comment - 2015-10-12 19:28

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.

centic added a comment - 2015-10-12 19:28 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.

dan tran added a comment - 2015-11-01 17:24

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

dan tran added a comment - 2015-11-01 17:24 jacoco version using 0.x, this means this sort of compatibility breakage is expected

centic added a comment - 2015-11-22 23:33

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.

centic added a comment - 2015-11-22 23:33 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.

centic made changes - 2015-11-22 23:33

Assignee	Ognjen Bubalo [ ognjenb ]	centic [ centic ]
Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]

Mark Waite added a comment - 2015-11-26 02:44

Verified closed with plugin version 2.0.0

Mark Waite added a comment - 2015-11-26 02:44 Verified closed with plugin version 2.0.0

Mark Waite made changes - 2015-11-26 02:44

Status

Resolved [ 5 ]

Closed [ 6 ]

Maninder Singh added a comment - 2016-02-02 18:46 - edited

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 my machine to plugin 1.0.19 for now. Which is working totally fine.

Maninder Singh added a comment - 2016-02-02 18:46 - edited 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 my machine to plugin 1.0.19 for now. Which is working totally fine.

Maninder Singh made changes - 2016-02-02 18:46

Resolution	Fixed [ 1 ]
Status	Closed [ 6 ]	Reopened [ 4 ]

AN2D added a comment - 2016-02-24 03:55

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

AN2D added a comment - 2016-02-24 03:55 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

Samuel Lopez added a comment - 2016-02-29 22:25

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)

Samuel Lopez added a comment - 2016-02-29 22:25 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)

centic added a comment - 2016-03-01 06:47

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.

centic added a comment - 2016-03-01 06:47 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.

AN2D added a comment - 2016-03-03 22:05

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

AN2D added a comment - 2016-03-03 22:05 Confirmed that Jacoco plugin version: 2.0.1 worked with the 0.7.6 version of jacocoagent.jar & jacocoant.jar. Thanks centic

centic added a comment - 2016-03-04 06:42

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.

centic added a comment - 2016-03-04 06:42 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.

centic made changes - 2016-03-04 06:42

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

Samuel Lopez added a comment - 2016-03-04 17:23

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

Samuel Lopez added a comment - 2016-03-04 17:23 Thanks, On my side it looks like using the Mvn plugin at 0.7.5 fixes my issue

Mark Waite made changes - 2016-03-15 14:41

Status

Resolved [ 5 ]

Closed [ 6 ]

bhalachandra bhat added a comment - 2016-06-07 12:22

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

bhalachandra bhat added a comment - 2016-06-07 12:22 I am also facing the same issue and i am not able to fix that

bhalachandra bhat added a comment - 2016-06-07 12:26

[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

bhalachandra bhat added a comment - 2016-06-07 12:26 [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

R. Tyler Croy made changes - 2016-07-26 00:01

Workflow

JNJira [ 163505 ]

JNJira + In-Review [ 208832 ]

Manish Kumar made changes - 2019-08-29 13:30

Attachment

Screenshot 2019-08-29 at 6.59.03 PM.png [ 48545 ]

Manish Kumar added a comment - 2019-08-29 13:32

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

Manish Kumar added a comment - 2019-08-29 13:32 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 Waite added a comment - 2019-08-29 13:47

manishkumar087 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.

Mark Waite added a comment - 2019-08-29 13:47 manishkumar087 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.

Jenkins

JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates