# Overview

## 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-community-build/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md) fails.

With Jenkins, you can suspend pipeline execution until the analysis’ quality gate status is known. See the [Key features](/sonarqube-community-build/analyzing-source-code/ci-integration/jenkins-integration/key-features.md) integration pages.

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).

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).

For other CIs, you can use the `sonar.qualitygate.wait=true` analysis parameter in your configuration file. Setting `sonar.qualitygate.wait` to true forces the analysis step to poll your SonarQube Community Build instance until the quality gate status is available. This increases the pipeline duration and causes the analysis step to fail any time the quality gate fails, even if the actual analysis is successful. You should only use this parameter if it’s necessary.

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

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

For GitLab CI/CD configuration, see the [Adding analysis to GitLab CI/CD pipeline](/sonarqube-community-build/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-community-build/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-community-build/devops-platform-integration/azure-devops-integration/adding-analysis-to-pipeline.md) page.

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

For Bitbucket Pipelines configuration, see the [Adding analysis to Bitbucket pipeline](/sonarqube-community-build/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-community-build/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-community-build/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.