---
-title: Running Analysis with GitLab CI/CD
+title: GitLab CI/CD
url: /analysis/gitlab-cicd/
---
-
_Merge Request analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._
-SonarScanners running in GitLab CI/CD Jobs will automatically detect branches or Merge Requests being built so you don't need to specifically pass them as parameters to the scanner.
+SonarScanners running in GitLab CI/CD jobs can automatically detect branches or Merge Requests being built so you don't need to specifically pass them as parameters to the scanner.
[[warning]]
-| You need to disable shallow clone to make sure the scanner has access to all of the branches when running analysis with GitLab CI/CD. See [Git shallow clone](https://docs.gitlab.com/ee/user/project/pipelines/settings.html#git-shallow-clone) for more on disabling shallow clone.
+| You need to disable git shallow clone to make sure the scanner has access to all of your history when running analysis with GitLab CI/CD. For more information, see [Git shallow clone](https://docs.gitlab.com/ee/user/project/pipelines/settings.html#git-shallow-clone).
## Activating builds
-Set up your build according to the section below that corresponds to your SonarQube edition.
-
-### Developer Edition and above
-By default, GitLab will build all branches but not Merge Requests. To build Merge Requests, you need to update the `.gitlab-ci.yml` file by adding `merge_requests` to the `only` parameter. See the **Example configurations** below for more information.
+Set up your build according to your SonarQube edition as described below.
### Community Edition
-Because Community Edition doesn't support branches, you should only analyze your main branch. You can restrict analysis to your main branch by adding the branch name to the `only` parameter.
+Because Community Edition doesn't support multiple branches, you should only analyze your main branch. You can restrict analysis to your main branch by adding the branch name to the `only` parameter.
+
+### Developer Edition and above
+By default, GitLab will build all branches but not Merge Requests. To build Merge Requests, you need to update the `.gitlab-ci.yml` file by adding `merge_requests` to the `only` parameter. See the example configurations below for more information.
## Failing the pipeline job when the SonarQube Quality Gate fails
In order for the Quality Gate to fail on the GitLab side when the Quality Gate fails on the SonarQube side, the scanner needs to wait for the SonarQube Quality Gate status. To enable this, set the `sonar.qualitygate.wait=true` parameter in the `.gitlab-ci.yml` file.
You can set the `sonar.qualitygate.timeout` property to an amount of time (in seconds) that the scanner should wait for a report to be processed. The default is 300 seconds.
-See the **Example configurations** below for more information.
+See the example configurations below for more information.
## Example configurations
The following example configurations show you how to configure the execution of SonarScanner for Gradle, SonarScanner for Maven, and SonarScanner CLI with GitLab CI/CD.
The `SONAR_TOKEN` and `SONAR_HOST_URL` variables are included. If you don't have environment variables set for all builds in GitLab's settings (as shown in **Setting environment variables for all builds** below), you need to set the variables to pass a [token](/user-guide/user-token/) and the URL of your SonarQube server.
-### SonarScanner for Gradle:
-
-```
-image: gradle:alpine
-variables:
- SONAR_TOKEN: "your-sonarqube-token"
- SONAR_HOST_URL: "http://your-sonarqube-instance.org"
- GIT_DEPTH: 0
-sonarqube-check:
- stage: test
- script: gradle sonarqube -Dsonar.qualitygate.wait=true
- allow_failure: true
- only:
- - merge_requests
- - master
-```
-
-### SonarScanner for Maven:
+Click your scanner below to see the example configuration:
+
+[[collapse]]
+| ## SonarScanner for Gradle:
+| ```
+| image: gradle:alpine
+| variables:
+| SONAR_TOKEN: "your-sonarqube-token"
+| SONAR_HOST_URL: "http://your-sonarqube-instance.org"
+| GIT_DEPTH: 0
+| sonarqube-check:
+| stage: test
+| script: gradle sonarqube -Dsonar.qualitygate.wait=true
+| allow_failure: true
+| only:
+| - merge_requests
+| - master
+| ```
-```
-image: maven:latest
-variables:
- SONAR_TOKEN: "your-sonarqube-token"
- SONAR_HOST_URL: "http://your-sonarqube-url"
- GIT_DEPTH: 0
-sonarqube-check:
- script:
- - mvn verify sonar:sonar -Dsonar.qualitygate.wait=true
- allow_failure: true
- only:
- - merge_requests
- - master
-```
-
-### SonarScanner CLI:
-
-```
-image:
- name: sonarsource/sonar-scanner-cli:latest
- entrypoint: [""]
-variables:
- SONAR_TOKEN: "your-sonarqube-token"
- SONAR_HOST_URL: "http://your-sonarqube-instance.org"
- GIT_DEPTH: 0
-sonarqube-check:
- stage: test
- script:
- - sonar-scanner -Dsonar.qualitygate.wait=true
- allow_failure: true
- only:
- - merge_requests
- - master
-```
-
-**Note:** A project key has to be provided through `sonar-project.properties` or through the command line parameter. For more information, see the [SonarScanner](/analysis/scan/sonarscanner/) documentation.
+[[collapse]]
+| ## SonarScanner for Maven:
+|
+| ```
+| image: maven:latest
+| variables:
+| SONAR_TOKEN: "your-sonarqube-token"
+| SONAR_HOST_URL: "http://your-sonarqube-url"
+| GIT_DEPTH: 0
+| sonarqube-check:
+| script:
+| - mvn verify sonar:sonar -Dsonar.qualitygate.wait=true
+| allow_failure: true
+| only:
+| - merge_requests
+| - master
+| ```
+
+[[collapse]]
+| ## SonarScanner CLI:
+|
+| ```
+| image:
+| name: sonarsource/sonar-scanner-cli:latest
+| entrypoint: [""]
+| variables:
+| SONAR_TOKEN: "your-sonarqube-token"
+| SONAR_HOST_URL: "http://your-sonarqube-instance.org"
+| GIT_DEPTH: 0
+| sonarqube-check:
+| stage: test
+| script:
+| - sonar-scanner -Dsonar.qualitygate.wait=true
+| allow_failure: true
+| only:
+| - merge_requests
+| - master
+| ```
+|
+| **Note:** A project key has to be provided through `sonar-project.properties` or through the command line parameter. For more information, see the [SonarScanner](/analysis/scan/sonarscanner/) documentation.
## Setting environment variables for all builds
Instead of specifying environment variables in your `.gitlab-ci.yml` file (such as `SONAR_TOKEN` and `SONAR_HOST_URL`), you can set them securely for all pipelines in GitLab's settings. See [Creating a Custom Environment Variable](https://docs.gitlab.com/ee/ci/variables/#creating-a-custom-environment-variable) for more information.
## For more information
-For more information on configuring your build with GitLab CI/CD, see the [GitLab CI/CD Pipeline Configuration Reference](https://gitlab.com/help/ci/yaml/README.md).
+For more information on configuring your build with GitLab CI/CD, see the [GitLab CI/CD Pipeline Configuration Reference](https://gitlab.com/help/ci/yaml/README.md).
\ No newline at end of file
---
## Release 8.3 Upgrade Notes
+
**Analysis summary for GitHub Pull Requests**
* Pull Request analysis can be shown under the Conversation tab in GitHub. You can enable or disable it at **Project Settings > General Settings > Pull Request Decoration**.
* If you already have Pull Request analysis under the GitHub Checks tab, you'll need to update your GitHub App to give Pull Requests read & write access. For more information see [Decorating Pull Requests](/analysis/pr-decoration/). ([MMF-1892](https://jira.sonarsource.com/browse/MMF-1892)).
+**Jenkins Automatic Branch and Pull Request Detection**
+With [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), Scanners now automatically detects branches and Pull Requests in Jenkins Multibranch Pipelines. You no longer need to pass branch and Pull Request parameters. When upgrading from Community Edition or an old commercial edition version, the branch name in your SonarQube project needs to match the branch name in your code repository to continue writing history to the branch. Because SonarQube renames the Main Branch "master" by default, you may have to rename it before running analysis again. See the [Jenkins CI Integration](/analysis/jenkins/) page for more information. ([MMF-1676](https://jira.sonarsource.com/browse/MMF-1676)).
+
## Release 8.2 Upgrade Notes
**Security Hotspots: dedicated space and workflow**
* The Security Hotspots have a brand new space where developers can perform security reviews. The review process has been simplified. It's no longer necessary to transform a Security Hotspot into a Manual Vulnerability and back. A developer can now simply mark a Security Hotspot as Safe, Fixed, or leave it as-is if more time is needed. ([MMF-1868](https://jira.sonarsource.com/browse/MMF-1868)).
* A Security Hotspots Reviewed metric has been added and is available to Quality Gates along with the Security Review Rating.
**New project homepage**
-The project homepage has been redesigned to focus on New Code ([MMF-1886](https://jira.sonarsource.com/browse/MMF-1886)). Projects details are now tucked into a new "Project information" pane. The project administration menu has been renamed "Project Settings".
+The project homepage has been redesigned to focus on New Code. ([MMF-1886](https://jira.sonarsource.com/browse/MMF-1886)). Projects details are now tucked into a new "Project information" pane. The project administration menu has been renamed "Project Settings".
**Deprecated configuration**
The old way of referencing environment variables in server configuration is deprecated and replaced with the support of default environment variables. ([SONAR-13113](https://jira.sonarsource.com/browse/SONAR-13113)).
**GitLab Authentication now available**
GitLab OAuth2 authentication is now available in all editions. If you were using the community plugin, you need to remove it from SonarQube before upgrading. The configured variable of the plugin will be migrated, so the authentication will work without having to rewrite the configuration. Due to changes in group mapping, GitLab subgroups mapped using the community plugin will need to be renamed in SonarQube for the mapping to work. ([SONAR-12460](https://jira.sonarsource.com/browse/SONAR-12460)).
-**New Code Period values simplified**
+**New Code Period values simplified**
It's now easier to set your New Code Period in the UI. With the new settings, specific analysis has replaced setting the New Code Period to a specific date or version. If you were using a specific date or version for your New Code Period, now you'll need to use a specific analysis. See the [Setting Your New Code Period](/project-administration/new-code-period/) for more info. ([MMF-1579](https://jira.sonarsource.com/browse/MMF-1579)).
[Full Release Notes](https://jira.sonarsource.com/secure/ReleaseNote.jspa?projectId=10930&version=14962)
**Pylint should be run manually**
Running Pylint automatically during python analysis has been deprecated. Additionally, it is broken in this version on Windows. If needed, Pylint must be run ahead of time and the resulting report passed in to analysis.
-[Full Release Notes](https://jira.sonarsource.com/secure/ReleaseNote.jspa?projectId=10930&version=14945)
-
-
-## Release 7.8 Upgrade Notes
-**MySQL Deprecation and Migration**
-This is the last version that will support MySQL. To migrate from MySQL to a supported database, see the free [MySQL Migrator tool](https://github.com/SonarSource/mysql-migrator).
-
-**Elasticsearch bootstrap checks enforced**
-SonarQube will now fail to start if Elasticsearch's bootstrap checks fail. That means you may need to [adjust the maximum number of open files and processes](/requirements/requirements/) for the SonarQube user as part of this upgrade ([SONAR-11264](https://jira.sonarsource.com/browse/SONAR-11264)).
-
-**Scanner version compatibility**
-Only the following scanner versions are compatible with SonarQube 7.8:
-* SonarQube Scanner CLI 2.9+
-* SonarQube Scanner Maven 3.3.0.603+
-* SonarQube Scanner Gradle 2.3+
-
-**Analysis fails with old branch parameter**
-`sonar.branch` was deprecated in 6.7. With this version analysis fails when it is used. Where it is still in use, simply remove the `sonar.branch` property and update your `sonar.projectKey` value to `key:branch`.
-
-**Notifications changes**
-Several changes have been made to notificatons. The notifications algorithm has been replaced with one that offers better performance during background task processing. Issue change notifications spawned by analysis or bulk change now generate only one email per event rather than one email per issue. The ability to subscribe globally to new issues notifications and notifications for issues resolved as False Positive or Won't fix has been dropped, as have all such subscriptions. Issue-related notifications on PRs have also been dropped.
-
-**Webhook payloads now signed**
-It is now possible to verify that webhook payloads actually come from SonarQube via the `X-Sonar-Webhook-HMAC-SHA256` HTTP header. ([SONAR-12000](https://jira.sonarsource.com/browse/SONAR-12000))
-
-**Graceful shutdown**
-The SonarQube server now shuts down gracefully. I.E. it completes any currently-processing background tasks before shutting down. This may mean that shutdown takes longer than previously. ([SONAR-12043](https://jira.sonarsource.com/browse/SONAR-12043))
-
-**Duplication density correction**
-A bug affecting the calculation of duplication density has been fixed. Each project's duplication density value will likely rise at the next analysis, possibly affecting Quality Gate status. ([SONAR-12188](https://jira.sonarsource.com/browse/SONAR-12188))
-
-**Additional authentication methods embedded**
-The SAML and GitHub Authentication plugins are now embedded in all editions ([SONAR-11894](https://jira.sonarsource.com/browse/SONAR-11894))
-
-**Deprecated web services dropped**
-Web services that were deprecated in 5.x versions have been dropped. ([SONAR-11876](https://jira.sonarsource.com/browse/SONAR-11876))
-
-[Full Release Notes](https://jira.sonarsource.com/secure/ReleaseNote.jspa?projectId=10930&version=14939)
-
-## Release 7.7 Upgrade Notes
-**Deprecated parameters dropped**
-`sonar.language`, and `sonar.profile`, both deprecated since 4.5, are dropped in this version as is `sonar.analysis.mode`, which as been deprecated since 6.6. These now-unrecognized parameters will simply be ignored, rather than failing analysis.
-
-**PR decoration below GitHub Enterprise 2.14 swapped for GitHub checks**
-This version adds support for GitHub Enterprise (GHE) checks, which were introduced in GHE 2.14, and drops support for PR decoration in GHE versions prior to 2.14. To use the new checks implementation, an application will need to be created in GHE, and further configuration will be required via the SonarQube UI. ([Details in the docs.](/instance-administration/github-application/).)
-
-**ElasticSearch update requires index rebuild, potentially more filespace**
-While it is generally possible to keep ElasticSearch indices in an upgrade (see [Configuring the Elasticsearch storage path](/setup/install-server/)), this version's upgrade of ElasticSearch will force all indices to be rebuilt. Additionally, more filespace may be required for this version's data ([SONAR-11826](https://jira.sonarsource.com/browse/SONAR-11826)).
-
-**32-bit architecture support dropped**
-Support for 32-bit architectures has been dropped as part of this version's upgrade of ElasticSearch, and those scripts removed from the distributions.
-
-**Deprecated metrics dropped**
-Several deprecated ([SONAR-1794](https://jira.sonarsource.com/browse/SONAR-11794)) or obsolete ([SONAR-11664](https://jira.sonarsource.com/browse/SONAR-11664)) metrics have been dropped from the platform.
-
-[Full Release Notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14848)
-
-## Release 7.6 Upgrade Notes
-**Quality Gates Simplified**
-Quality Gates have been streamlined to remove a number of confusing options. Conditions previously using the "on new code" checkbox will be migrated to On New Code metrics. For example, a condition previously using the overall Coverage metric with the "on new code" checkbox enabled will be migrated to a condition using the Coverage on New Code metric. The ability to set Warning conditions has been dropped, as have some metric/operator conditions have been removed. Conditions using dropped options will be removed in the upgrade. ([MMF-473](https://jira.sonarsource.com/browse/MMF-473))
-
-**Concept of module removed from the UI**
-This version drops the concept of module from the interface. There is no longer a homepage presentation for any level below the project itself. Additionally, the presentation of the project has been updated in the Measures and Code pages to display the project tree as it is in the file system. For the most part (see below) analysis of multi-module projects will continue to work as it has.
-
-**Multi-Module analysis properties removed**
-Multi-module analysis configuration may need to be changed ([MMF-365](https://jira.sonarsource.com/browse/MMF-365)):
-
-* When exclusions based on file paths are specified in the analysis properties at project level, those file paths must be relative to the project / analysis root. Paths specified at project level will continue to be re-applied at module level but will raise a warning. This backward-compatibile behavior is considered deprecated and will be dropped in a future version.
-* Specifying source encoding, and issue inclusions / exclusions at module level is no longer supported.
-
-**Incompatibility with Findbugs plugin version 3.9.1 and earlier**
-This version embeds SonarHTML, which analyzes both `.html` and `.jsp` files. Because of this change, the community plugin Findbugs versions 3.9.1 and earlier are incompatible with SonarQube 7.6+ ([MMF-1567](https://jira.sonarsource.com/browse/MMF-1567)).
-
-[Full Release Notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14693)
-
-## Release 7.5 Upgrade Notes
-**More Issues Backdated**
-Additional cases of issue backdating have been added, so fewer genuinely old issues will be reported in the New Code period ([MMF-1287](https://jira.sonarsource.com/browse/MMF-1287))
-
-**Two Vulnerabilities Patched**
-An open redirect vulnerability on login was corrected ([SONAR-11475](https://jira.sonarsource.com/browse/SONAR-11475)).
-
-An XSS vulnerability in custom project links was also patched. ([SONAR-11506](https://jira.sonarsource.com/browse/SONAR-11506)).
-
-**Deadlock Fixed**
-The deadlock that could occur with the combination of
-* SQL Server
-* Multiple workers
-* Analysis of projects and portfolios
-
-has been fixed ([SONAR-11467](https://jira.sonarsource.com/browse/SONAR-11467)).
-
-**DB Connection Pool Defaults Restored**
-Database connection pool defaults have been restored to their pre-SonarQube 7.4 values. They were inadvertently affected by a change of connection pooling in 7.4 ([SONAR-11539](https://jira.sonarsource.com/browse/SONAR-11539)).
-
-**Database Name in JDBC URL Now Case-Sensitive**
-For MSSQL users, a driver upgrade rendered the database name case-sensitive in the JDBC URL ([SONAR-11443](https://jira.sonarsource.com/browse/SONAR-11443)).
-
-[Full Release Notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14693)
-
-
-## Release 7.4 Upgrade Notes
-**Analysis Failure on Invalid New Code Period**
-Analysis will fail if the New Code Period (see below) is not set to one of:
-* valid, in-the-past date
-* positive integer (number of days)
-* `previous_version`
-* the version string of an existing snapshot
-
-For more, see [SONAR-10555](https://jira.sonarsource.com/browse/SONAR-10555)
-
-**New Create Portfolios and Create Applications permissions**
-Two distinct new create permissions have been added. Users who have any creation permission will see a new "+" item in the top menu giving access to these permissions. For more, see the Global Permissions topic in [Security](/instance-administration/security/)
-
-**Issues from third party Roslyn analyzers**
-Analyzing a C# / VB.NET solution now automatically imports issues found by attached Roslyn analyzers into SonarQube, and no longer suppresses them from the MSBuild output. The Quality Gate status of projects may be impacted.
-
-**More memory may be needed for analysis**
-Changes in the advanced security analysis available in Developer Edition and above may mean that a larger heap is needed during analysis.
-
-**Analysis warnings in UI**
-Some `WARN` messages generated during analysis are now available via the UI ([MMF-1244](https://jira.sonarsource.com/browse/MMF-1244)). More messages will be available as new versions of language analyzers are released.
-
-**"Leak" replaced with "New Code"**
-Wording has been updated throughout the interface to replace "Leak" and "Leak Period" with "New Code" and "New Code Period".
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14549)
-
-
-## Release 7.3 Upgrade Notes
-
-**New "Administer Security Hotspots" Permission**
-During the upgrade, the new "Administer Security Hotspots" permission is granted to all users/groups who already have the "Administer Issues" permission.
-
-**Expanded Compute Engine Logs**
-Starting with this version, Compute Engine logs will be more verbose. These logs are rotated automatically, but on a daily basis, not based on file size.
-
-**PostgreSQL < 9.3 No Longer Supported**
-SonarQube 7.3+ only supports PostgreSQL 9.3 to 10. SonarQube will not start if you are using a lower version of PostgreSQL.
-
-**Some 3rd-party Plugins Incompatible**
-APIs deprecated before SonarQube 5.6 are dropped in this version, making some third-party plugins incompatible. It is always advised to check plugin compatibility in the Plugin Version Matrix with each new upgrade, and more so for this version.
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14464)
-
-## Release 7.2 Upgrade Notes
-
-**License Incompatibility**
-**Users coming from 6.7.5 must not upgrade to this version.** Your license will be incompatible. Instead, if you seek an upgrade to an intermediate version before the next L.T.S. version, you must start from 7.3 or higher.
-
-**Pull Request Analysis**
-Pull Requests are now a first class citizen feature in SonarQube for Developer, Enterprise and Data Center Edition users.
-
-If you are using GitHub, you need to be sure to NOT have the GitHub Plugin in your SONARQUBE_HOME/extensions/plugins directory.
-
-**New Edition Packaging**
-SonarSource Commercial Editions are now distributed individually, so you directly get the features and functionalities that match your needs. This means that upgrade/downgrade from one edition to another is no longer possible within the SonarQube Marketplace. In order to use a different edition you must download its dedicated package, and have a license ready for using that edition.
-
-**Deprecated Features**
-SonarQube 7.2 is the last version supporting PostgreSQL < 9.3. Starting from SonarQube 7.3 the minimal supported version of PostgreSQL will be 9.3: SONAR-10668
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14213)
-
-## Release 7.1 Upgrade Notes
-
-**License Incompatibility**
-**Users coming from 6.7.5 must not upgrade to this version.** Your license will be incompatible. Instead, if you seek an upgrade to an intermediate version before the next L.T.S. version, you must start from 7.3 or higher.
-
-**Live Portfolios**
-Portfolio measures are now updated without having to explicitly trigger recalculation. As a result, the "views" scanner task no longer has any effect, and will fail with a clear error message.
-
-**Deprecated Features**
-Support for MySQL is deprecated for all editions below Data Center Edition (see below).
-
-**Dropped Features**
-- Support for MySQL in Data Center Edition.
-- The "accessors" metric, which was deprecated in SonarQube 5.0.
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14178)
-
-## Release 7.0 Upgrade Notes
-
-**License incompatibility**
-**Users coming from 6.7.5 must not upgrade to this version.** Your license will be incompatible. Instead, if you seek an upgrade to an intermediate version before the next L.T.S. version, you must start from 7.3 or higher.
-
-**Measures: Live Update**
-Project measures, including the Quality Gate status, are computed without having to trigger another code scan when issue changes may impact them.
-
-**Built-In Read-Only Quality Gate**
-In order to make clear the default, minimum and recommended criteria Quality Gates, the "Sonar way" Quality Gate is now read-only, and the default if one is not already set. It may be updated automatically at each upgrade of SonarQube.
-
-**Dropped Features**
-It's no longer possible to unset the default Quality Gate.
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14041)
-
-
-## Release 6.7.5 Upgrade Notes
-
-**Commercial Edition Must Be Upgraded**
-Because a new server identifier will be generated at upgrade to this version, startup will fail unless you upgrade your commercial edition to the latest compatible version. I.E. don't just copy over your edition plugins from one instance to the next, but make sure to download the latest edition bundle.
-
-**SonarLint Must Be Upgraded**
-Analyzers provided as part of a commercial package will be disabled in old versions of SonarLint. SonarLint users must upgrade to the latest available version:
-
-- SonarLint for Eclipse: 3.3+.
-- SonarLint for IntelliJ: 3.1+
-
-**Multi-Version Upgrade**
-Don't forget to read all the intermediate upgrade notes if you're upgrading more than a single version.
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=14467)
-
-
-## Release 6.7 Upgrade Notes
-
-**Drop of Issues Report**
-The deprecated Issues Report feature has been removed.
-
-[Full release notes](https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=13972)
+[Full Release Notes](https://jira.sonarsource.com/secure/ReleaseNote.jspa?projectId=10930&version=14945)
\ No newline at end of file
projects / sonarqube.git / commitdiff