Overview

SonarQube Server supports integration on multiple platforms allowing you to maintain code quality and security in your projects.

Pull request analysis is available as part of Developer Edition and above.

Failing a pipeline job when the quality gate fails

You can ensure your code meets your quality standards by failing your pipeline job when your quality gate fails. The operation depends on the CI tool used.

JENKINS

With Jenkins, you can suspend pipeline execution until the analysis’ quality gate status is known. See the Setting up a pipeline pause integration pages.

GITHUB

With GitHub Actions, you can fail the pipeline job when the quality gate fails using the SonarQube Quality Gate Check Action.

BITBUCKET PIPELINES

With Bitbucket Pipelines, you can fail the pipeline job when the quality gate fails using the SonarQube Quality Gate Check Pipe.

OTHER CI TOOLS

You can configure the SonarScanner to wait for the quality gate result. This setting will force the pipeline to fail if the quality gate fails.

To do so:

1. Set the sonar.qualitygate.wait analysis parameter to true.

2. You can set the sonar.qualitygate.timeout analysis parameters to the number of seconds that the scanner should wait for a report to be processed. The default is 300 seconds.

For general information on setting up analysis parameters, see Analysis parameters and the respective SonarScanner section: SonarScanner for Maven, SonarScanner for Gradle, Configuring the scanner, Configuring the scanner, SonarScanner for Python, or SonarScanner CLI.

GitLab CI/CD

For GitLab CI/CD configuration, see the Adding analysis to GitLab CI/CD pipeline page.

GitHub Actions

For GitHub Actions configuration, see the Introduction page.

Azure Pipelines

For Azure Pipelines configuration, see the Introduction section.

Bitbucket Pipelines

For Bitbucket Pipelines configuration, see the Bitbucket Cloud integration page.

Jenkins

For Jenkins configuration, see Jenkins extension.