Pull Request Analysis
Pull Request analysis is available starting in Developer Edition.
You can see your Pull Requests in SonarQube from the Branches and Pull Requests dropdown menu of your project.
Pull Request analysis shows your Pull Request's Quality Gate and analysis in the SonarQube interface. This analysis shows new issues introduced by the Pull Request before merging with the target branch:
Before analyzing your Pull Requests, make sure the Pull Request branch is checked out. Avoid any attempt at previewing the merge or actions involving your main branch.
Pull request decoration
You can also add pull request decoration that shows the Pull Request analysis and Quality Gate directly in your ALM's interface. To set up pull request decoration, see the ALM integration page that corresponds with your ALM:
Pull request Quality Gate
A Quality Gate lets you ensure you are meeting your organization's quality policy and that you can merge your pull request. The pull request uses your project Quality Gate as follows:
- Focuses on new code – The Pull Request quality gate only uses your project's quality gate conditions that apply to "on New Code" metrics.
- Assigns a status – Each Pull Request shows a quality gate status reflecting whether it Passed or Failed.
Pull request analyses on SonarQube are deleted automatically after 30 days with no analysis. This can be updated in Administration > Configuration > General Settings > Housekeeping > Number of days before purging inactive branches.
The following parameters enable PR analysis.
Scanners running on Jenkins with the Branch Source plugin configured, GitLab CI/CD, Bitbucket Pipelines, Azure Pipelines, and Cirrus CI automatically detect these parameters, and you don't need to pass them manually.
|Unique identifier of your Pull Request. Must correspond to the key of the Pull Request in your ALM.|
|The name of the branch that contains the changes to be merged.|
|The branch into which the Pull Request will be merged. |