Code Analyzis is not done anymore with sonarqube-gradle-plugin:2.3 ?

[Culda Sergiu]

Hi everybody,

Today I just changed sonarqube java project analyzer from org.sonarqube.gradle:gradle-sonarqube-plugin:1.1 to org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.3.

With gradle-sonarqube-plugin:1.1, when I run sonarqube task from Eclipse I got some logs into Console:
example:
INFO: SonarQube Server 6.3.0.19869
11:20:55.762 INFO  - Load global settings
11:20:55.907 INFO  - Load global settings (done) | time=148ms
11:20:55.939 INFO  - User cache: C:\Users\Administrator\.sonar\cache
11:20:57.318 INFO  - Load plugins index
11:20:57.325 INFO  - Load plugins index (done) | time=7ms
11:20:58.185 INFO  - Process project properties
11:20:58.333 INFO  - Load project repositories
11:20:58.534 INFO  - Load project repositories (done) | time=201ms
11:20:59.969 INFO  - Load quality profiles
11:21:00.005 INFO  - Load quality profiles (done) | time=36ms
11:21:00.012 INFO  - Load active rules
11:21:00.488 INFO  - Load active rules (done) | time=476ms
11:21:00.490 INFO  - Load metrics repository
11:21:00.609 INFO  - Load metrics repository (done) | time=119ms
11:21:00.626 INFO  - Publish mode
11:21:00.627 INFO  - Project key: project
11:21:00.633 INFO  - -------------  Scan PROJECT
11:21:01.029 INFO  - Load server rules
11:21:01.189 INFO  - Load server rules (done) | time=160ms
11:21:01.359 INFO  - Initializer GenericCoverageSensor
11:21:01.360 INFO  - Initializer GenericCoverageSensor (done) | time=1ms
11:21:01.361 INFO  - Base dir: C:\workspace\project
11:21:01.361 INFO  - Working dir: C:\workspace\project\build\sonar
11:21:01.363 INFO  - Source paths: src/main/resources, src/main/java
11:21:01.363 INFO  - Test paths: src/test/java
11:21:01.363 INFO  - Source encoding: windows-1252, default locale: en_GB
11:21:01.366 INFO  - Index files
11:21:01.388 INFO  - 18 files indexed
11:21:01.390 INFO  - Quality profile for java: Sonar way with Findbugs
11:21:01.568 INFO  - Sensor JavaSquidSensor [java]
11:21:01.958 INFO  - Configured Java source version (sonar.java.source): 8
11:21:01.981 INFO  - JavaClasspath initialization
11:21:02.024 INFO  - JavaClasspath initialization (done) | time=43ms
11:21:02.024 INFO  - JavaTestClasspath initialization
11:21:02.026 INFO  - JavaTestClasspath initialization (done) | time=2ms
11:21:02.549 INFO  - Java Main Files AST scan
11:21:02.553 INFO  - 16 source files to be analyzed
11:21:03.574 WARN  - Metric 'public_documented_api_density' is an internal metric computed by SonarQube. Provided value is ignored.
11:21:03.602 WARN  - Metric 'lines' is an internal metric computed by SonarQube. Provided value is ignored.
11:21:08.174 INFO  - Java Main Files AST scan (done) | time=5625ms
11:21:08.174 INFO  - Java Test Files AST scan
11:21:08.174 INFO  - 1 source files to be analyzed
11:21:08.178 INFO  - 16/16 source files have been analyzed
11:21:08.244 INFO  - Java Test Files AST scan (done) | time=70ms
11:21:08.244 INFO  - Sensor JavaSquidSensor [java] (done) | time=6676ms
11:21:08.244 INFO  - Sensor PmdSensor [pmd]
11:21:08.252 INFO  - Execute PMD 5.4.0...
11:21:08.332 INFO  - 1/1 source files have been analyzed
11:21:08.334 INFO  - Java version: 1.8
.
.
not relevant
.
.
11:21:27.276 INFO  - org.sonar.scanner.cpd.deprecated.JavaCpdBlockIndexer@307e88f0 is used for java
11:21:27.410 INFO  - Sensor CPD Block Indexer (done) | time=135ms
11:21:27.444 INFO  - Calculating CPD for 15 files
11:21:27.509 INFO  - CPD calculation finished
11:21:27.867 INFO  - Analysis report generated in 342ms, dir size=497 KB
11:21:27.962 INFO  - Analysis reports compressed in 93ms, zip size=167 KB
11:21:28.043 INFO  - Analysis report uploaded in 81ms
11:21:28.044 INFO  - ANALYSIS SUCCESSFUL, you can browse http://

After changing the plugin to org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.3. The output of code analyze is not provided into CONSOLE.

Can anyone tell me if the code analyze is still done?


[Julien HENRY]

Hi,

We updated the plugin to log using Gradle standard logging facility. Gradle is very quiet by default, you should add --info argument to see the SonarQube Scanner analysis logs.

++

Julien