I saw that in the documentation for the latest 7.6 release, the Pull Request Analysis does not include Bitbucket as a sonar.pullrequest.provider. Any updates regarding this feature? It’s now supported for the on-premise version?
Thank you.
I’ve split this from the 5-month-old version release announcement you posted it on to a new thread, since it’s really not related to that old announcement.
We anticipate releasing SonarQube 7.7 with support for BitBucket Server.
You can check out the documentation on generating your personal access token on BitBucket Server here. You need to make sure the account that you’re using to decorate your PRs has write permission.
I am a SonarQube user, currently with SonarQube 7.7 Developer Edition and have PR analysis working with Bitbucket Server 6.3.0. First, you need to have Bitbucket Server 5.15 or greater for PR decoration as the the PR integration uses the Bitbucket Insights API.
In SonarQube Server, go to Administration → General Settings → Pull Requests, set provider to Bitbucket Server and access token
In my sonar-project.properties, I have:
sonar.pullrequest.bitbucketserver.project=PROJ
sonar.pullrequest.bitbucketserver.repository=MYREPO
sonar.projectVersion=${buildVersion}
sonar.pullrequest.branch=${buildGitBranch}
sonar.pullrequest.key=${buildPullRequestId}
sonar.pullrequest.base=${buildPullRequestTargetBranch}
I run this through Jenkins CI (with SonarQube gating) and works great.
I just have another question regarding Bitbucket cloud, as it seams that the authentication mechanism requires an access_token (personal access token).
I looked for this in Bitbucket cloud and it seams that they offer “App passwords” instead. @scmbuildguy Will this work in Sonarqube as a secured token?