You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR decoration (BitBucket server) produces a feedback on the BitBucket pull request page with Analysis Details. Unfortunately the message from SonarQube occupies whole screen and after few updates to the PR it becomes unreadable. The problem is the messages have big "icons" (white squares) which causes to be the message so long.
At the end of the message a link http://localhost:9000/dashboard?id=project&pullRequest=1 appears which directs to the server of bitbucket while (in our case, any probably not only our) the sonarqube is located on different host.
To Reproduce
Steps to reproduce the behavior:
BB server v7.2.2
SonarQube 7.9.3 (LTS)
sonarqube-community-branch-plugin-1.3.0
Expected behavior
The "icons" are not higher than fonts or can be disabled/customized
The links points to the actual sonarqube server
The text was updated successfully, but these errors were encountered:
The URLs are driven by the configuration you've put into Sonarqube for what your server base URL is, and this value defaults to localhost if you've not set it otherwise. An administrator needs to set the Server Base URL value under Administration > Configuration > General settings to the correct URL for your Sonarqube instance.
Describe the bug
Two issues:
PR decoration (BitBucket server) produces a feedback on the BitBucket pull request page with Analysis Details. Unfortunately the message from SonarQube occupies whole screen and after few updates to the PR it becomes unreadable. The problem is the messages have big "icons" (white squares) which causes to be the message so long.
At the end of the message a link http://localhost:9000/dashboard?id=project&pullRequest=1 appears which directs to the server of bitbucket while (in our case, any probably not only our) the sonarqube is located on different host.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The text was updated successfully, but these errors were encountered: