> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/ci-based-analysis/other-cis.md).

# Other CIs

Running an analysis on a CI provider other than those with specific integrations.

## Running an analysis on another CI provider

1. Integrate the SonarScanner analysis into your build pipeline as explained in the corresponding scanner section:
   * [SonarScanner for .NET](/sonarqube-cloud/analyzing-source-code/scanners/sonarscanner-for-dotnet.md)
   * [SonarScanner for Maven](/sonarqube-cloud/analyzing-source-code/scanners/sonarscanner-for-maven.md),
   * [SonarScanner for Gradle](/sonarqube-cloud/analyzing-source-code/scanners/sonarscanner-for-gradle.md)
   * [SonarScanner for NPM](/sonarqube-cloud/analyzing-source-code/scanners/sonarscanner-for-npm.md)
2. If necessary, adjust the [Analysis scope](/sonarqube-cloud/managing-your-projects/project-analysis/setting-analysis-scope.md) or customize other default [Analysis parameters](/sonarqube-cloud/analyzing-source-code/analysis-parameters.md).
3. Start and test the analysis.
4. Add the branch analysis or pull request analysis to your pipeline. See the [Branch analysis setup](/sonarqube-cloud/analyzing-source-code/branch-analysis/branch-analysis-setup.md) and [Pull request analysis](/sonarqube-cloud/analyzing-source-code/pull-request-analysis.md) pages for more information.

Here is an example of a configuration for pull requests in a CI job:

```properties
sonar.pullrequest.base=main
sonar.pullrequest.branch=feature/my-new-feature
sonar.pullrequest.key=5
```

If your project is bound to Azure DevOps and you're running analysis outside of Azure Pipelines, you must also pass Azure DevOps-specific parameters explicitly. Azure Pipelines detects these values automatically from its environment; other CI systems don't. See [Parameters not settable in the UI](/sonarqube-cloud/analyzing-source-code/analysis-parameters/parameters-not-settable-in-ui.md#azure-devops-pr-decoration-parameters) for more information about these parameters.

## 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](/sonarqube-cloud/analyzing-source-code/analysis-parameters/configuration-overview.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/ci-based-analysis/other-cis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.