[ https://issues.apache.org/jira/browse/CALCITE-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645391#comment-17645391 ]
Stamatis Zampetakis commented on CALCITE-5427: ---------------------------------------------- An example of how things will look like when the integration is done can be seen here: https://sonarcloud.io/summary/overall?id=org.apache.calcite%3Acalcite > Provide code quality/coverage metrics with SonarCloud and JaCoCo > ---------------------------------------------------------------- > > Key: CALCITE-5427 > URL: https://issues.apache.org/jira/browse/CALCITE-5427 > Project: Calcite > Issue Type: Improvement > Components: build > Reporter: Stamatis Zampetakis > Assignee: Stamatis Zampetakis > Priority: Major > Fix For: 1.33.0 > > > Provide code quality and coverage metrics for the master branch and every PR > to facilitate code reviews, improve security, and protect against regressions > by exploiting SonarCloud and JaCoCo. > [SonarCloud|https://sonarcloud.io/] is popular platform for providing code > quality insights and widely used by [ASF > projects|https://sonarcloud.io/organizations/apache/projects]. > [JaCoCo|https://www.jacoco.org/jacoco/trunk/index.html] relies on > instrumentation via a java agent to gather code coverage information while > running tests. > The integration in the Calcite build can be done via Gradle plugins and the > analysis will be triggered automatically via GitHub actions. Appropriate > configuration properties will be added ensure that local builds will not be > impacted. > Initially, the code quality metrics will have purely informational character > and will be at the discretion of the reviewer to enforce or ignore them. > Later on, we can decide and agree on code quality gates which can be enforced > automatically by SonarCloud and JaCoCo. It is possible to enforce things > mostly at CI level but certain things can also be applied on local builds. -- This message was sent by Atlassian Jira (v8.20.10#820010)