Closed malcolm061990 closed 2 years ago
The issue is solved. Now I get decorated PRs. The only change was to specify explicitly to what commit id do I need to send the decoration. It can be done via parameter in sonar-project.properties or via cli:
sonar.scm.revision=$sourceCommitHash
The $sourceCommitHash
env var contains the source commit id :)
Describe the bug There is no PR decoration in Bitbucket Server.
To Reproduce Steps to reproduce the behavior:
Branch Source
plugin in jenkins. We useStash pull request builder
plugin that provides all required vars to SonarQube Scanner. We don't use Multibranch Pipelines, we use just Freestyle projects in jenkins.sonarqube-community-branch-plugin
. It's shown in SonarQube UI, so all is ok with its installation.We have here that must mean all is good:
UPD: Sonraqube sends report to automatic merge commit instead of last commit in PR. Logs from sonarqube in trace mode.
where
154b1894d1ea18efe41d4bdb3c5783af43e40deb
- automatic merge commit474a467560b1484bc87dc619ade6887051412cf1
- last commit But I think SonarQube must send report to the last commit in PR, not to automatic merge commitWe have in SonarQube UI (than means there is a PR):
The PR in BitBucket is NOT decorated :(
Expected behavior PR has decoration.
Software Versions