[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.146326.1350570861000.6131.1572535860677%40Atlassian.JIRA.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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:*/com/company/product//config//.coverage-exclusion-01> /com/company/cfa//CallDTO.coverage-exclusion-02> */com/company/cfa/*/DAO.coverage-exclusion-03> And I use them to configure the maven jacoco plugin ${coverage-exclusion-01}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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.146326.1350570861000.5677.1568754240860%40Atlassian.JIRA.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Ognjen Bubalo commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Check this: https://groups.google.com/d/topic/jenkins-jacoco-plugin-mailing-list/LCWg0ukJ_wg/discussion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Ognjen Bubalo commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Hi, Hopefully I'll implement this feature and release a new version in the next 2 days. Cheers, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Thomas Zlika commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Yes, the problem is still present with the latest 1.0.9 version. I have some packages excluded from code coverage using the "excludes" parameter of the jacoco-maven-plugin. The HTML page generated by this plugin are correct (the excludes packages are not taken into account). However, the Jenkins plugin take them into account and display a code coverage of 0%. The configuration for the Jenkins plugin is the standard one: Path to exec files: **/target/jacoco.exec Path to class dir: **/target/classes Path to source dir: **/src/main/java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. jacoco's version is: 0.6.1.201212231917. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. jacoco's version is: 0.6.1.201212231917. Maybe the Jenkins-Plugin should just drop all .class files where no .java files are found? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. jacoco's version is: 0.6.1.201212231917. Maybe the Jenkins-Plugin should just drop all .class files where no .java files are found? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Ognjen Bubalo started work on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Change By: Ognjen Bubalo (27/Dec/12 3:17 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Ognjen Bubalo commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Is this issue still actual? If yes, please show your configuration (given paths) of JaCoCo. Thanks, ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
David Barri commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis I'm having this issue too. The relevant part of my POM looks like this: plugin groupIdorg.jacoco/groupId artifactIdjacoco-maven-plugin/artifactId version0.6.0.201210061924/version executions execution idcoverage-agent/id phaseprocess-test-classes/phase goals goalprepare-agent/goal /goals /execution execution idcoverage-report/id phasetest/phase goals goalreport/goal /goals /execution /executions configuration excludes !-- Exclude classes generated by AndroidAnnotations -- exclude**/*_.*/exclude exclude**/*_$*/exclude /excludes /configuration /plugin When I generate a Jacoco HTML report, classes that end in an underscore like ExampleActivity_ do not appear because of the exclude settings in my POM. However from Jenkins all of those classes that the Maven build excludes are visible again. My Jenkins settings for this plugin are the defaults. Thanks! David This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Rune Flobakk commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis I am guessing this is related to classes which are generated, e.g. from WSDLs. A common use case is to generate Java source files which end up in target/generated-sources/**. This folder then becomes part of the source folder of the project, and compiled as usual into target/classes and packaged as usual. But these classes should not be part of the coverage report. In my case, I have a Maven module which only purpose is to generate such classes and package them into a jar. The module does not even have a src-folder because everything is generated from WSDLs/XSDs. The jacoco-maven-plugin correctly does not produce any jacoco.exec file for this module, but it seems like the Jenkins plugin sees the output classes, and no jacoco.exec, and interprets that as zero coverage. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Ognjen Bubalo commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Hi, Please give us more information. Which plugin version do you use? What is your current configuration on the configuration page of JaCoCo plugin? Cheers, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Darrell King created JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 18/Oct/12 2:34 PM Description: In my Maven config there are a number of classes that are excluded from Jacoco analysis. The report generated by Jacoco does not include these classes. The report generated by the Jenkins Jacoco plugin does includes these classes which gives a misleading picture and makes it difficult to set any coverage thresholds. I think this may be related to JENKINS-14975. Project: Jenkins Labels: jacoco Priority: Minor Reporter: Darrell King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
