# Not integrated CI tools

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

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](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/analysis-parameters/configuration-overview "mention").

## Related pages

* [github-actions](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/ci-integration/github-actions "mention")
* [bitbucket-pipelines](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/ci-integration/bitbucket-pipelines "mention")
* [gitlab-ci-cd](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/ci-integration/gitlab-ci-cd "mention")
* [azure-pipelines](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/ci-integration/azure-pipelines "mention")
* [jenkins-integration](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/ci-integration/jenkins-integration "mention")
* [codemagic-integration](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/ci-integration/codemagic-integration "mention")