[
https://issues.apache.org/jira/browse/SLING-11400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556423#comment-17556423
] Ashok Pelluru commented on SLING-11400: --------------------------------------- [~kwin]: Can we directly execute `-Pjacoco-report` at [https://github.com/apache/sling-tooling-jenkins/blob/master/vars/slingOsgiBundleBuild.groovy#L163] ? so we will get coverage XML files to analyse sonar in the next stage? it's removed from [https://github.com/apache/sling-tooling-jenkins/commit/3782cb94c511db8693306ec74d43f678d15d5d0f#diff-b563d1b8523d30b2e9ee4bf280c97142d5f45078b5abd0f31af2751d08512e5aL59] [https://github.com/apache/sling-tooling-jenkins/commit/3782cb94c511db8693306ec74d43f678d15d5d0f#diff-b563d1b8523d30b2e9ee4bf280c97142d5f45078b5abd0f31af2751d08512e5aR223] (mvn clean verify is missing to reuse the build artifacts maybe) > Jacoco coverage was missing on PR > --------------------------------- > > Key: SLING-11400 > URL: https://issues.apache.org/jira/browse/SLING-11400 > Project: Sling > Issue Type: Bug > Components: Build and Source Control > Reporter: Ashok Pelluru > Priority: Major > > It seems like, after recent changes, jacoco test coverage was missing on pull > requests: > jacoco test coverage plugin itself is not executing > *jacoco-maven-plugin* > > Example PR: > [https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/pull/10] > > > Build Console: > [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-scripting-sightly-compiler/view/change-requests/job/PR-10/1/console] > -- This message was sent by Atlassian Jira (v8.20.7#820007)
