# SonarQube extension for Jenkins
SonarScanner for Jenkins — 2.18 | Issue Tracker **2.18** **2025-01-28**\ Minor updates\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010138%20AND%20fixVersion%20%3D%2015464) *** **2.17.3** **2024-11-18**\ Update dependencies to improve security\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010138%20AND%20fixVersion%20%3D%2016121) *** **2.17.2** **2024-02-19**\ Fix withSonarQubeEnv step hanging when the workspace contains a symlink\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010138%20AND%20fixVersion%20%3D%2015473) *** **2.16.1** **2023-10-10**\ Bug fixes\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010138%20AND%20fixVersion%20%3D%2015332) *** **2.16** **2023-09-27**\ Use the sonar.token property\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010138%20AND%20fixVersion%20%3D%2013951) *** **2.15** **2022-11-22**\ Fixed out of memory when querying deleted projects\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010138%20AND%20fixVersion%20%3D%2013860) *** **2.14** **2021-11-18**\ Prepare SonarQube Scanner for core Guava upgrade\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project+%3D+10138+AND+fixVersion+%3D+12438) *** **2.13.1** **2021-04-30**\ Update dependencies\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project+%3D+10138+AND+fixVersion+%3D+12437) *** **2.12** **2020-09-07**\ Improve use of SonarQube configuration, bug fixes\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project+%3D+10138+AND+fixVersion+%3D+12435) *** **2.11** **2020-01-06**\ Improvements for Jenkins Configuration as Code\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project+%3D+10138+AND+fixVersion+%3D+12434) *** **2.10** **2019-10-19**\ Add webhook validation based on a shared secret\ [Download](https://plugins.jenkins.io/sonar/)\ \ [Release notes](https://sonarsource.atlassian.net/issues/?jql=project+%3D+10138+AND+fixVersion+%3D+12433)
This extension lets you centralize the configuration of SonarQube server connection details in Jenkins global configuration. Then you can trigger SonarQube analysis from Jenkins using standard Jenkins Build Steps or [Jenkins Pipeline DSL](https://jenkins.io/solutions/pipeline/) to trigger analysis with the SonarScanner. Once the job is complete, the extension will detect that a SonarQube analysis was made during the build and display a badge and a widget on the job page with a link to the SonarQube dashboard as well as quality gate status. See: * [Key features](/sonarqube-server/10.5/analyzing-source-code/ci-integration/jenkins-integration/key-features.md) * [Setting up Jenkins](/sonarqube-server/10.5/analyzing-source-code/ci-integration/jenkins-integration/global-setup.md) * [Adding analysis to a Jenkins job](/sonarqube-server/10.5/analyzing-source-code/ci-integration/jenkins-integration/add-analysis-to-job.md) * [Setting up a pipeline pause](/sonarqube-server/10.5/analyzing-source-code/ci-integration/jenkins-integration/pipeline-pause.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-server/10.5/analyzing-source-code/scanners/jenkins-extension-sonarqube.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.