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?
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!
Michael from Mibex Software
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs