[JIRA] (JENKINS-59813) JacocoPublisher (part of pipeline-maven) does not deal with excludes properly
Title: Message Title Cyrille Le Clerc commented on JENKINS-59813 Re: JacocoPublisher (part of pipeline-maven) does not deal with excludes properly Work In Progress: JacocoPublisher settings only support a `disabled` flag. See https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.8.2/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JacocoReportPublisher.java#L254 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.202545.1571276714000.2112.1573902060250%40Atlassian.JIRA.
[JIRA] (JENKINS-59813) JacocoPublisher (part of pipeline-maven) does not deal with excludes properly
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-59813 JacocoPublisher (part of pipeline-maven) does not deal with excludes properly Change By: Cyrille Le Clerc Issue Type: Bug Improvement 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.202545.1571276714000.1605.1573813740637%40Atlassian.JIRA.
[JIRA] (JENKINS-59813) JacocoPublisher (part of pipeline-maven) does not deal with excludes properly
Title: Message Title Jeffrey Bennett commented on JENKINS-59813 Re: JacocoPublisher (part of pipeline-maven) does not deal with excludes properly Found a work-around of sorts. Completely disable the JacocoPublisher and use the external 'jacoco' step instead. Since the latter accepts exclude, it can be properly configured. If you don't disable the JacocoPublisher, you wind up with two similar looking reports in Jenkins. 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.202545.1571276714000.13240.1571755200205%40Atlassian.JIRA.
[JIRA] (JENKINS-59813) JacocoPublisher (part of pipeline-maven) does not deal with excludes properly
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-59813 JacocoPublisher (part of pipeline-maven) does not deal with excludes properly Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-10-17 01:45 Priority: Major Reporter: Jeffrey Bennett The jacoco report published by pipeline indicates classes that should have been excluded. Our build, a multi-module maven build executes jacoco on multiple modules. In the POM, we indicate on a number of classes (generated java). When built by maven (command-line), the jacoco report is properly created - excluded files are properly excluded. When we wrapper this build into a jenkinsfile and invoke it via a withMaven(..), the JacocoPublisher kicks in. The jacoco report on the Jenkins job appears to include the excluded files. It looks to me like JacocoPublisher is reinvoking Jacoco-Plugin with default parameters. The Jacoco-Plugin output shows a blank line for 'exclude', which explains why the report has things it should not. I suspect the easiest solution is to offer a parameter on JacocoPubisher that would pass-through to the Jacoco-Plugin. This would allow people to write Jenkinsfiles, enter the 'excludes' they desire, and Jacoco-Plugin would then run properly.
