You’ve said “Bitbucket Cloud” in the title of this thread. Since your other systems are self-managed, I want to confirm that that one’s actually the cloud service?
In global Administration → DevOps Platform Integrations, when you Check configuration does it come back as green / well configured?
And can you check your ce.logserver log to see if it says anything?
I’m a little confused: what do you expect to see in Bitbucket? In your example, the Quality Gate is passed, so I don’t expect to see anything specific on your PR. Furthermore, we don’t do inline comments on Bitbucket; we submit what Bitbucket calls a “report”, and this report contains the details. But, if there’s nothing in the report (everything green), well, then you will only see “Quality Gate passed”.
OK, can you please check your sonar.core.serverBaseURL setting (in conf/sonar.properties)? Changing it will require restarting SonarQube. If this setting is not correct, Bitbucket Cloud will not be able to communicate back to SonarQube, and pushing a report with annotations will fail.
sonar.core.serverBaseURL was set to company internal IP. At outside, we can not access this IP, because it is in internal network in company as I mentioned.
In company network, I can access this IP and use sonarQube properly.
Can you change it to an IP or hostname that Bitbucket Cloud can access (don’t forget to restart)? For pull request decoration to work, Bitbucket Cloud needs to check the request is legit, and to do this, it contacts the SonarQube server. If it cannot reach SonarQube, the pull request decoration cannot happen.
I understood the limitation of sonarQube. I believed that PR decorations can works well because I thought that data for decorations sent from local sonarQube to Bitbucket by one way.