[
https://issues.apache.org/jira/browse/HIVE-26196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Solimando updated HIVE-26196:
----------------------------------------
Summary: Integrate Sonar analysis for the master branch and PRs (was:
Integrate Sonar analysis for the master branch)
> Integrate Sonar analysis for the master branch and PRs
> ------------------------------------------------------
>
> Key: HIVE-26196
> URL: https://issues.apache.org/jira/browse/HIVE-26196
> Project: Hive
> Issue Type: Improvement
> Components: Build Infrastructure
> Affects Versions: 4.0.0-alpha-2
> Reporter: Alessandro Solimando
> Assignee: Alessandro Solimando
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The aim of the ticket is to integrate SonarCloud analysis for the master
> branch.
> The ticket does not cover:
> * test coverage
> * analysis on PRs and other branches
> Those aspects can be added in follow-up tickets, if there is enough interest.
> From preliminary tests, the analysis step requires 30 additional minutes for
> the pipeline.
> The idea for this first integration is to track code quality metrics over new
> commits in the master branch, without any quality gate rules (i.e., the
> analysis will never fail, independently of the values of the quality metrics).
> An example of analysis is available in my personal Sonar account:
> [https://sonarcloud.io/summary/new_code?id=asolimando_hive]
> ASF offers SonarCloud accounts for Apache projects, and Hive already has one
> (https://sonarcloud.io/project/configuration?id=apache_hive, created via
> INFRA-22542), for completing the present ticket, somebody having admin
> permissions in that repo should generated an authentication token, which
> should replace the _SONAR_TOKEN_ secret in Jenkins.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
