# Scanners - [Scanner environment](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/scanner-environment.md): Information on scanner environment requirements, TLS certificates, and checked out code. - [General requirements](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/scanner-environment/general-requirements.md): General requirements for setting up your SonarScanner for SonarQube Server. - [TLS certificates on client side](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/scanner-environment/manage-tls-certificates.md): If your SonarQube Server instance is secured, add the self-signed certificate to the CI/CD host. If mutual TLS is used, an additional setup is required. - [Checked-out code](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/scanner-environment/verifying-code-checkout-step.md): During the checkout of a working copy (clone) of the code from the project repository, we recommend using the full depth. - [Managing JRE auto-provisioning](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/scanner-environment/managing-jre-auto-provisioning.md): How to disable or adjust JRE auto-provisioning for scanners. - [SonarScanner CLI](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarscanner.md): The SonarScanner CLI is a code analysis scanner for CI/CD pipelines, used when no build-system-specific scanner is available. Distinct from the SonarQube CLI, a developer management interface. - [Azure DevOps Extension](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops.md): The Azure DevOps extension for SonarQube Server makes it easy to integrate analysis into your build pipeline, allowing you to analyze all supported languages. - [Jenkins extension](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/jenkins-extension-sonarqube.md): This extension lets you centralize the configuration of your SonarQube Server connection details in your Jenkins global configuration. - [SonarScanner for Maven](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarscanner-for-maven.md): The SonarScanner for Maven is recommended as the default scanner for Maven projects. - [SonarScanner for Gradle](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarscanner-for-gradle.md): The SonarScanner for Gradle provides an easy way to start the analysis of a Gradle project with SonarQube Server. - [SonarScanner for .NET](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/dotnet.md): Information on installing, using, and configuring the SonarScanner for .NET. - [Introduction](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/dotnet/introduction.md): Your entry point to understanding how the SonarScanner for .NET works with SonarQube Server. - [Installing the scanner](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/dotnet/installing.md): Installing the SonarScanner for .NET to run with SonarQube Server is easy. Everything you need to know is on this page. - [Using the scanner](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/dotnet/using.md): Check this page to learn how to invoke the SonarScanner for .NET and understand which parameters to use in your SonarQube Server analysis. - [Configuring the scanner](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/dotnet/configuring.md): Configuring the SonarScanner for .NET in SonarQube Server can be tricky. Here is everything you need to know. - [SonarScanner for NPM](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/npm.md): This section describes how to install, use, and configure the sonarScanner for NPM. - [Introduction](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/npm/introduction.md): The SonarScanner for NPM makes it very easy to trigger a SonarQube Server analysis on your JavaScript code base, without needing additional tools or resources. - [Installing the scanner](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/npm/installing.md): Depending on how you want to start the SonarScanner for NPM, you will use a different method to install the scanner. - [Using the scanner](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/npm/using.md): To start the SonarScanner for NPM, you can either add the analysis to your build files or use the scanner start command line (with or without npx). - [Configuring the scanner](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/npm/configuring.md): This section explains how to configure the parameters used for an analysis with the SonarScanner for NPM when running it with SonarQube Server. - [SonarScanner for Python](https://docs.sonarsource.com/sonarqube-server/2026.2/analyzing-source-code/scanners/sonarscanner-for-python.md): The SonarScanner for Python provides an easy way to start the analysis of a Python project with SonarQube Server. --- # 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/2026.2/analyzing-source-code/scanners.md?ask= ``` 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.