Sonarcloud is analysing PRs via bitbucket pipeline, but not main branch?

[ganncamp (G Ann Campbell)]

Hi,

We’ve covered this multiple times. Here’s one excerpt, emphasis added:

@ganncamp

You need to edit your branch pattern.

And since staging was initially created as a short-lived branch, you’ll need to delete it and re-create it after you’ve corrected the pattern. Branch types are immutable.

When you re-create it, make sure to do so without passing a branch name parameter. This means it will be created as main in SonarCloud. You can then rename it to staging.

It seems you want develop to act as the primary branch in the project currently under consideration. The rules are the same:

• Analyze develop without passing a sonar.branch.name parameter. Since branch names are picked up automatically by the integrations, you may need to run this first analysis manually.
• Via the SonarQube Cloud UI, rename the main branch to develop
• Analyze as normal. Further analyses of the sonar.branch.name=develop branch will land in the project’s primary branch

@nutmix

how do we get sonar to analyze the main repo, not just the PRs , and to use develop, not master?

I assume you’re asking here about which branch the PR is compared to? If so, it’s largely a question of making sure the prerequisites are in place.

 
HTH,
Ann