I'm using
When I create a new pull request the stats show no issues in bit bucket. However when I look at the project on the sonar server it shows one new bug and two new code smells. In bitbucket Sonar is configured to show all issues, Min. severity to show is set to MINOR, and analysis mode is set to Branch-based. Both branches involved in the pull request have project on the sonar server.
Any ideas on what could be causing this issue?
Hi,
This is probably because the plug-in was not able to deduce the right component keys for the files in the pull request to get information from the Sonar server.
To analyze why this happens, I need the debug logs of the plug-in.
1) Could you therefore please enable debug logging for the plug-in? You can do this under Bitbucket admin -> Sonar -> "Enable debug logging".
2) Then, please clear the cache in the repository settings of the plug-in by selecting the "Advanced" tab and clicking on the "Invalidate cache" button.
3) Finally, please open the pull request where the problem occurs again. If you could then send me all lines containing "SONAR:" from your BITBUCKET_HOME/log/atlassian-bitbucket.log file (to our support e-mail address), that would help me much!
Best regards,
Michael from Mibex Software
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.