> 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

To run an analysis on a CI provider other than those with specific integrations:

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
```


---

# 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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.