[
https://issues.apache.org/jira/browse/HIVE-29180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018052#comment-18018052
]
Stamatis Zampetakis commented on HIVE-29180:
--------------------------------------------
The Jenkins logs contain various suspicious warnings during the Sonar
execution. One that seems particularly worrisome is the following:
{noformat}
[2025-09-03T13:29:27.390Z] [INFO] SCM collecting changed files in the branch
[2025-09-03T13:29:27.390Z] [WARNING] Could not find ref: master in refs/heads,
refs/remotes/upstream or refs/remotes/origin
[2025-09-03T13:29:27.390Z] [INFO] SCM collecting changed files in the branch
(done) | time=11ms
{noformat}
> SonarQube reports issues unrelated to changes in the pull request
> -----------------------------------------------------------------
>
> Key: HIVE-29180
> URL: https://issues.apache.org/jira/browse/HIVE-29180
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Attachments: sonarqube-bad-report.png
>
>
> SonarQube runs on every pull request and performs static code analysis
> notifying contributors and reviewers about potential issues in the code.
> Lately, SonarQube started reporting way too many issues that are clearly
> unrelated to the changes in the pull request and this seems to affect every
> new PR that is submitted on GitHub.
> One such example can be seen in:
> https://github.com/apache/hive/pull/6049#issuecomment-3237772048
> The problem was first reported in the dev list:
> https://lists.apache.org/thread/m36fc3dldd23nj8mncdjmzx33k87flm5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
