# Overview

*Pull request analysis is available as part of* [*Developer Edition*](https://www.sonarsource.com/plans-and-pricing/developer/) *and* [*above*](https://www.sonarsource.com/plans-and-pricing/)*.*

## Failing a pipeline job when the quality gate fails <a href="#quality-gate-fails" id="quality-gate-fails"></a>

You can ensure your code meets your quality standards by failing your pipeline job when your [quality gate](https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/analysis-functions/quality-gates) fails. The operation depends on the CI tool used.

{% tabs %}
{% tab title="JENKINS" %}
With Jenkins, you can suspend pipeline execution until the analysis’ quality gate status is known. See the [pipeline-pause](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/ci-integration/jenkins-integration/pipeline-pause "mention") integration page.
{% endtab %}

{% tab title="GITHUB" %}
With GitHub Actions, you can fail the pipeline job when the quality gate fails using the [SonarQube Quality Gate Check Action](https://github.com/marketplace/actions/sonarqube-quality-gate-check).
{% endtab %}

{% tab title="BITBUCKET PIPELINES" %}
With Bitbucket Pipelines, you can fail the pipeline job when the quality gate fails using the [SonarQube Quality Gate Check Pipe](https://bitbucket.org/sonarsource/sonarqube-quality-gate).
{% endtab %}

{% tab title="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 about setting up analysis parameters at the global and project levels, see [analysis-parameters](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/analysis-parameters "mention") and the respective SonarScanner section: [sonarscanner-for-maven](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/scanners/sonarscanner-for-maven "mention"), [sonarscanner-for-gradle](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/scanners/sonarscanner-for-gradle "mention"), [configuring](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/scanners/dotnet/configuring "mention"), [configuring](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/scanners/npm/configuring "mention"), or [sonarscanner](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/scanners/sonarscanner "mention").
{% endtab %}
{% endtabs %}

## GitLab CI/CD <a href="#gitlab" id="gitlab"></a>

For GitLab CI/CD configuration, see the [adding-analysis-to-gitlab-ci-cd](https://docs.sonarsource.com/sonarqube-server/2025.1/devops-platform-integration/gitlab-integration/adding-analysis-to-gitlab-ci-cd "mention") page.

## GitHub Actions <a href="#github-actions" id="github-actions"></a>

For GitHub Actions configuration, see the [adding-analysis-to-github-actions-workflow](https://docs.sonarsource.com/sonarqube-server/2025.1/devops-platform-integration/github-integration/adding-analysis-to-github-actions-workflow "mention") page.

## Azure Pipelines <a href="#azure-pipelines" id="azure-pipelines"></a>

For Azure Pipelines configuration, see the [adding-analysis-to-pipeline](https://docs.sonarsource.com/sonarqube-server/2025.1/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline "mention") section.

## Bitbucket Pipelines <a href="#bitbucket-pipeline" id="bitbucket-pipeline"></a>

For Bitbucket Pipelines configuration, see the [#analyzing-projects-with-bitbucket-pipelines](https://docs.sonarsource.com/sonarqube-server/2025.1/devops-platform-integration/bitbucket-integration/bitbucket-cloud-integration#analyzing-projects-with-bitbucket-pipelines "mention") page.

## Jenkins <a href="#jenkins" id="jenkins"></a>

For Jenkins configuration, see [add-analysis-to-job](https://docs.sonarsource.com/sonarqube-server/2025.1/analyzing-source-code/ci-integration/jenkins-integration/add-analysis-to-job "mention").