Details
-
Test
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.0.0-alpha-2
-
None
Description
The analysis for the master branch was using the wrong variable name (CHANGE_BRANCH) instead of the branch name (BRANCH_NAME).
For an overview of git-related environment variables available in Jenkins, you can refer to https://ci.eclipse.org/webtools/env-vars.html/.
With zabetak we have noticed some spurious files in Sonar analysis for PRs, as per this sonar support thread it might be linked to the stale analysis of the target branch (master for us): https://community.sonarsource.com/t/unrelated-files-scanned-in-sonarcloud-pr-check/47138/14
Attachments
Issue Links
- depends upon
-
HIVE-26196 Integrate Sonar analysis for the master branch and PRs
- Closed
- links to