Popular Posts

SonarQube Tutorial

SonarQube Documentation

SonarQube Documentation

SonarQube® software (previously called Sonar) is an open source quality management platform, dedicated to continuously analyze and measure technical quality, from project portfolio to method.

SonarQube Vs SonarLint Vs SonarScanner

  1. SonarQube is a central server that processes full analyses (triggered by the various SonarQube Scanners). Its purpose is to give a 360° vision of the quality of your code base. For this, it analyzes all the source lines of your project on a regular basis.

  2. SonarLint lives only in the IDE (IntelliJ, Eclipse and Visual Studio). Its purpose is to give instantaneous feedback as you type your code. For this, it concentrates on what code you are adding or updating. Both SonarLint and SonarQube rely on the same static source code analyzers - most of them being written using SonarSource technology.

  3. SonarScanners(Recommended) is a plugin that can be integrated with your build system which scans and sends results to standalone SonarQube Server. Plugin available for Maven,Gradle and Ant build systems. This is recommended way to integrated with your project source code.

  4. SonarRunner : is an old name for SonarScanner.

Installing SonarQube locally with docker

Run following command to start sonar server in your local

$/>docker run -d --name sonarqube -p 9000:9000 -p 9092:9092 sonarqube

Default installation of SonarQube runs at 9000 port with following credentials.





Point your browser to http://localhost:9000 and enter credentials to login. it will prompt you to create token.

Generate token :

Name of the token : MyOrgName

Generated Token : 6f715af92650b0843948f8c26f1f335611dad996

This token won’t work for your server. This is just demonstration purpose only. you need to generate from your server instance.
The token is used to identify you when an analysis is performed. If it has been compromised, you can revoke it at any point of time in your user account. When sonar.forceAuthentication is set to 'true'. we need this token to be included in the sonar configuration.

Integrating SonarQube Scanner with Gradle Project

The SonarQube Scanner for Gradle provides an easy way to start SonarQube analysis of a Gradle project.

The ability to execute the SonarQube analysis via a regular Gradle task makes it available anywhere Gradle is available (developer build, CI server, etc.), without the need to manually download, setup, and maintain a SonarQube Scanner installation.

SonarQube plugin for Groovy

This plugin enables analysis of Groovy within SonarQube.

It depends on the following sub-projects

  1. CodeNarc to raise issues against coding rules

  2. GMetrics for cyclomatic complexity

  3. Cobertura or Jacoco for code coverage.


The SonarQube Scanner for Gradle version 2.x is compatible with Gradle versions 1.12+ and SonarQube versions 5.6+


Installation is automatic, but certain global properties should still be configured. A good place to configure global properties is ~/.gradle/gradle.properties. Be aware that we are using System properties so all properties should be prefixed by systemProp.


#----- Security (when 'sonar.forceAuthentication' is set to 'true')

Alternatively create sonar.properties in project root director and add these properties without systemProp prefix.

# This is to show test coveate report on sonar UI
Jacoco , code coverage report will be created in the .exec format under build/jacoco. SonarQube will read and displays on the Web console.

Activate the scanner in your build.gradle

Add following snippet in build.gradle file

plugins {
    id 'jacoco'
    id "org.sonarqube" version "2.6.2"
only buildscript {} and other plugins {} script blocks are allowed before this code.

Jacoco Test Coverage with sonar

Add following code snippet to generate jacoco Report

// NOTE: jacoco always generate code coverage report with `.exec` extension which is not readable

jacocoTestReport {
    //make sure uniTest and layerTest are running before this jacocoTestReport
    //dependsOn unitTest
    reports {
        xml.enabled true
        csv.enabled false
        html.destination file("${buildDir}/jacocoHtml") //revisit this
Run analysis

Execute following command and wait until the build has completed, then open the web page indicated at the bottom of the console output. You should now be able to browse the analysis results.

$/>./gradlew sonarqube

Using Sonar in Production ready environment

Default sonar uses in-memory H2 database. if we are running sonar as docker image we need following command to run.

$ docker run -d --name sonarqube \
    -p 9000:9000 -p 9092:9092 \
    -e SONARQUBE_JDBC_URL=jdbc:postgresql://localhost/sonar \

alternatively we can deploy in kubernetes cluster

apiVersion: extensions/v1beta1
kind: Deployment
  name: sonar
  replicas: 1
      name: sonar
        app: sonar
        - image: sonarqube:6.0
            - -Dsonar.web.context=/
          name: sonar
            - name: SONARQUBE_JDBC_PASSWORD
                  name: db-info
                  key: password
            - name: SONARQUBE_JDBC_URL
                  name: db-info
                  key: url
            - containerPort: 9000
              name: sonar

Unrecognized files

By default, only files that are recognized by a language plugin are loaded into the project during analysis. For example if your SonarQube instance has the Java and JavaScript plugins on board, all .java and .js files will be loaded, but .xml files will be ignored. However, it is possible to import all text files in the analysis encoding in a project by setting Settings > Exclusions > Files > Import unknown files to true.

During Analysis

During analysis, data is requested from the server, the files provided to the analysis are analyzed, and the resulting data is sent back to the server at the end in the form of a report, which is then analyzed asynchronously server-side.

Analyzing with SonarQube Scanner for Jenkins

Refer link for complete details on to integrate with Jenkins

Customize Server Settings (TODO)

Adding SonarQube rules in java (TODO)

Writing coding rules in Java is a six-step process:

  1. Create a SonarQube plugin.

  2. Put a dependency on the API of the language plugin for which you are writing coding rules.

  3. Create as many custom rules as required

  4. Generate the SonarQube plugin (jar file)

  5. Place this jar file in the SONARQUBE_HOME/extensions/plugins directory

  6. Restart SonarQube server

Adding Custom Rules

Exclude Specific source files from analysis

The SonarQube Scanner for Gradle adds a SonarQubeExtension extension to project and its subprojects, which allows you to configure/override the analysis properties.

sonarqube {
    properties {
        property "sonar.exclusions", "**/*Generated.java"

No comments:

Post a Comment