[ https://issues.apache.org/jira/browse/FLINK-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837809#comment-15837809 ]
ASF GitHub Bot commented on FLINK-5092: --------------------------------------- Github user zentol commented on a diff in the pull request: https://github.com/apache/flink/pull/2836#discussion_r97788511 --- Diff: flink-contrib/flink-storm-examples/pom.xml --- @@ -364,6 +363,18 @@ under the License. </transformers> </configuration> </execution> + <execution> + <id>shade-flink</id> --- End diff -- With this we execute the shade-plugin also for other build-profiles, correct? (same for `flink-examples/flink-examples-streaming`) It would be cool if this would only be done when creating the coverage report, so that the normal build-time is unaffected. > Add integration with Sonarqube and code coverage > ------------------------------------------------ > > Key: FLINK-5092 > URL: https://issues.apache.org/jira/browse/FLINK-5092 > Project: Flink > Issue Type: Improvement > Components: Tests > Reporter: Boris Osipov > Assignee: Boris Osipov > > It would be good to have the opportunity to generate test coverage reports > for Flink and analyze code by SonarQube. > Parts of tasks: > - add generate test coverage reports for Flink with new maven profile > - implement integration with https://analysis.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)