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

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

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

Attachment

New: JENKINS-28652-JaCoCo-0.7.5-displays-no-coverage.xml [ 29870 ]

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

Attachment

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

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

Description

Original: 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

New: 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

Original: 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

New: 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

Original: 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]

New: 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

Original: 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]

New: 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

Original: 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]

New: 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

Original: 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]

New: 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 made changes - 2015-07-22 11:03

Link

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

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

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

Jenkins

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates