[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis

[christian.schulz@ewetel.net (JIRA)]

C. S. updated an issue

Jenkins / JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Change By: C. S. Priority: Minor Major Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[christian.schulz@ewetel.net (JIRA)]

C. S. commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis We ran into the same issue. It is important for us to get it working, because we have a lot of generated classes, which should be excluded and it would be a mess to set up each Jenkins job according the new classes. So we decided to exclude the classes from the report via pom. But it seems that the jacoco plugin does its own match from classes to exec file.

Add Comment

[raj.bhaskar@glasgow.ac.uk (JIRA)]

Raj Bhaskar commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

I think I'm having the same issue. I package the Oracle JDBC driver as a local jar in my application (as it's not on maven) but it looks like although I'm excluding it in my pom, the plugin is still including it when doing its analysis.

Add Comment

[zteve@skipjaq.com (JIRA)]

Steve Powell commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

This is an issue for us also. In a maven build with the jacoco plugin we exclude all the classes in a package; and jacoco reports in the console log that these have been excluded. In the jacoco check phase, no further inclusions/exclusions are supplied but thresholds are provided. The coverage report given by Jenkins seems to include those classes, the coverage percentages (package, line and so on) remaining the same as without exclusion. The threshold checks (in particular the line thresholds) still apply and make the build fail. The classes we exclude are generated into generated-sources by a third party (immutables.org) which we do not wish to test.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[antoine.tran@thales-services.fr (JIRA)]

Antoine Tran commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

We have this issue too. Right now, we need to duplicate exclusion information from pom.xml into this Jenkins Jacoco plugin. This issue is not solved yet.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[jgangemi@gmail.com (JIRA)]

Jae Gangemi commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

is there any futher movement on this issue? configuring exclusions in maven and jenkins is not a viable work around.

Add Comment

[ataylor@cloudbees.com (JIRA)]

Alex Taylor commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

I was looking into this issue and it appears that the Jacoco plugin fixed this issue for ENV variables with https://github.com/jenkinsci/jacoco-plugin/pull/74 but it does not actually parse the pom.xml for the `excludes`(or `includes` for that matter) configuration. Does that sound like the actual issue here rather than the Excludes not working at all?   Did I miss anything here? I was going to work on getting this fixed with a PR hopefully within the next week

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[jgangemi@gmail.com (JIRA)]

Jae Gangemi commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

i'm confused as to why this information just isn't part of the generated results file in the first place as a block that indicates what to exclude. perhaps even better would just be excluding the classes from the result file outright. disclaimer: i have not looked into how the maven plugin works when i choose to generate a report, but it does do the proper exclusions. if the plugin needs to parse the pom to figure this out, then that is the fix but that doesn't really seem like the correct solution here b/c what if i'm a nodejs project that is able to generate coverage reports in jacoco format? there's not going to be any pom to parse for exclusions in that case.

Add Comment

[gabe.stanek@gmail.com (JIRA)]

Gabriel Stanek commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

Alex Taylor , what you've described, regarding the exclude block in the maven plugin not taking affect in Jenkins, is the issue I've seen and am interested in a fix for, and seems to align with the initial description (which is specific to maven based projects).

Add Comment

[ataylor@cloudbees.com (JIRA)]

Alex Taylor commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

Thanks for the update Gabriel Stanek just wanted make sure I was understanding everyone's issue and how best I can fix it

Add Comment

[alan@czajkowski.ca (JIRA)]

Alan Czajkowski commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

really looking forward to this fix! lots of anxiety around this bug

Add Comment

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

[rajiv.jandial@pearson.com (JIRA)]

Rajiv Jandial commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

I am still seeing this as an open issue. Even I exclude the package from the pom.xml as well as from the Jenkins "exclusions" fields, those packages are still being included in the JaCoCo report.

Add Comment

[pablogrisafi1975@gmail.com (JIRA)]

Pablo Grisafi commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

my workaround: in the pom.xml I save all patterns  as properties: <coverage-exclusion-01>*/com/company/product//config//.</coverage-exclusion-01><coverage-exclusion-02>/com/company/cfa//CallDTO.</coverage-exclusion-02><coverage-exclusion-03>*/com/company/cfa/*/DAO.</coverage-exclusion-03> And I use them to configure the maven jacoco plugin <configuration> <excludes> <exclude>${coverage-exclusion-01}</exclude> <exclude>${coverage-exclusion-02}</exclude> etc...   And then, in the pipeline file y read again the properties   script{      props = readMavenPom().getProperties()     exclusionPattern = props.entrySet().findAll\{entry -> entry.key.startsWith('coverage-exclusion-')}.collect{it.value}.join(',')     echo "exclusionPattern = ${exclusionPattern}" } jacoco( execPattern: '**/target/jacoco.exec', exclusionPattern: exclusionPattern)   It works, but is ugly

Add Comment

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

[arielman22@gmail.com (JIRA)]

Ariel M commented on JENKINS-15570

Re: Coverage report includes classes that have been excluded from Jacoco analysis

We are also facing the same issue. it's weird coz' it's working for one MS, but not for the other. is there any update for it?

Add Comment