-
Notifications
You must be signed in to change notification settings - Fork 72
SonarQube finds no issues, and approves PR. #58
Comments
I've tried various times over the last few months with the latest version of both Sonarqube and the plugin. |
Could you please follow the instructions in the troubleshooting section (https://github.com/mibexsoftware/sonar-bitbucket-plugin#troubleshooting) and send me the debug log output of a build run? That would help me much. Thanks in advance! |
Sure thing, I apologize for missing that. I've done that and put it in a gist here. |
I've skimmed the logs a few times and didn't see any smoking guns, though it's quite a bit of output. |
I have the same issue. I am using MSBUILD Runner plugin. Sonarqube puts a comment on PR and says No issues. Take a chocolate. But I have put code purposely to receive comments. I also checked the sonarqube web and my latest code is not available there. This plugin appends the pull request id to project key and I think that's why it is not giving comments and not uploading the code to localhost:9000 |
It works in "preview" mode though. With issues mode, it is not commenting. |
I'm not sure it's supposed to upload the code in preview mode. |
Just to be clear, it is not uploading code in preview mode. It is giving proper comments on the pull request in preview mode. But in issues mode, it just asks us to take a chocolate! |
Hi, I too am seeing something similar. I committed code with a MAJOR violation and the plugin commented appropriately. Then I fixed that code and put in a BLOCKER violation and the plugin says have a chocolate. I have tried both PREVIEW and ISSUES mode and the same behavior occurs. SonarLint CLI and SonarLint for Intellij have correctly identified the problem and tell me before I commit. I also lowered the SEVERITY to INFO and the comment was updated by the sonar plugin to say that INFO and greater are monitored. Here is the stack:
|
I believe the issue comes from the fact that the plugin retrieves the changed lines from the PR in Bitbucket and will try to match analysed warnings with those changed lines. It can happen that the analysis detected your MAJOR issue but reported it with other line numbers than the ones you actually committed which would explain why sonar4bitbucket is ignoring them... |
Would posting a bounty from bountysource help get this issue towards the top of the list? I'd throw in. |
Just finished installing the plugin and getting everything running just to hit this bug. I hope someone will fix this because I really like the concept of the plugin. |
Same here. We use this plugin with SonarQube and Java projects with no problem. However we just got this setup with the MSBuild scanner for C# (.NET Core) projects and, while the issues show on SonarQube and in the scanner log, all that shows on the Bitbucket PR is "no issues take a chocolate". Edit: this ended up being a difference in the default Quality Profiles in SonarQube on the upgraded instance we were testing. Using the Troubleshooting link posted above helped sort things out. |
@nwoolls I've opened an issue but it might just be a duplicate of this one --> #90 |
Quoting another user, as I'm seeing the same thing:
Any tips? It's obviously found my PR, so I do have that setup correctly.
The text was updated successfully, but these errors were encountered: