[
https://issues.apache.org/jira/browse/HIVE-26196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577820#comment-17577820
]
Alessandro Solimando commented on HIVE-26196:
---------------------------------------------
Sure, on Jenkins side the token is handled in the credentials section:
[http://ci.hive.apache.org/credentials/]
On the SonarCloud side the token can be generated here:
[https://sonarcloud.io/account/security]
> 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: 2h
> Remaining Estimate: 0h
>
> The aim of the ticket is to integrate SonarCloud analysis for the master
> branch and PRs.
> The ticket does not cover test coverage at the moment (it 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, but this step is run in parallel with the test run, so the
> total end-to-end run-time is not affected.
> The idea for this first integration is to track code quality metrics over new
> commits in the master branch and for PRs, 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 the ASF Sonar account for Hive: [PR
> analysis|https://sonarcloud.io/summary/new_code?id=apache_hive&pullRequest=3254]
> After integrating the changes, PRs will also be decorated with a link to the
> analysis to be able to better evaluate any pain points of the contribution at
> an earlier stage, making the life of the reviewers a bit easier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
