# 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](/sonarqube-server/2025.5/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md) 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 [Key features](/sonarqube-server/2025.5/analyzing-source-code/ci-integration/jenkins-integration/key-features.md) integration pages.
{% 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).

See [Adding analysis to GitHub Actions workflow](/sonarqube-server/2025.5/devops-platform-integration/github-integration/adding-analysis-to-github-actions-workflow.md#fail-workflow-on-quality-gate-failure).
{% 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).

See [Adding analysis to Bitbucket pipeline](/sonarqube-server/2025.5/devops-platform-integration/bitbucket-integration/bitbucket-cloud-integration/bitbucket-pipelines.md#failing-the-pipeline-job-when-the-quality-gate-fails).
{% 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 on setting up analysis parameters, see [Configuration overview](/sonarqube-server/2025.5/analyzing-source-code/analysis-parameters/configuration-overview.md).
{% endtab %}
{% endtabs %}

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

For GitLab CI/CD configuration, see the [Adding analysis to GitLab CI/CD pipeline](/sonarqube-server/2025.5/devops-platform-integration/gitlab-integration/adding-analysis-to-gitlab-ci-cd.md) page.

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

For GitHub Actions configuration, see the [Adding analysis to GitHub Actions workflow](/sonarqube-server/2025.5/devops-platform-integration/github-integration/adding-analysis-to-github-actions-workflow.md) page.

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

For Azure Pipelines configuration, see the [Adding analysis to Azure pipeline](/sonarqube-server/2025.5/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline.md) section.

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

For Bitbucket Pipelines configuration, see the [Adding analysis to Bitbucket pipeline](/sonarqube-server/2025.5/devops-platform-integration/bitbucket-integration/bitbucket-cloud-integration/bitbucket-pipelines.md) page.

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

For Jenkins configuration, see [Adding analysis to a Jenkins job](/sonarqube-server/2025.5/analyzing-source-code/ci-integration/jenkins-integration/add-analysis-to-job.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.5/analyzing-source-code/ci-integration/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.