How to execute SonarQube scanner in Jenkins Declarative Pipeline without Maven and Docker

Ali Khawar picture Ali Khawar · Feb 1, 2018 · Viewed 11.9k times · Source

Does SonarQube scanner support BlueOcean pipeline plugin without maven and docker, if it does how does the script works in Jenkinsfile?

I'm new to Jenkins and BlueOcean and have tried all the basic possible aspects available.

If the SonarQube plugin did support Declarative:

pipeline {
  agent any
  stages {
    stage('SonarQube analysis') {
      tools {
        sonarQube 'SonarQube Scanner 2.8'
      }
      steps {
        withSonarQubeEnv('SonarQube Scanner') {
          sh 'sonar-scanner'
        }
      }
    }
  }
}

Answer

agabrys picture agabrys · Feb 1, 2018

We cannot say that the SonarQube scanner supports or does not support BlueOcean. BlueOcean is a presentation layer which displays data provided by stages (example: logs).

SonarQube scanner generates logs, so BlueOcean can displays it. I do not think that this type of relationship can be classified as a "support of".


EDIT:

You can execute an analysis in Declarative Pipeline by using the following code:

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                def scannerHome = tool 'SonarQubeScanner3'
                withSonarQubeEnv('SonarQube') {
                    sh "${scannerHome}/bin/sonar-scanner"
                }
            }
        }
    }
}

You have also add a SonarQube server in Manage Jenkins → Configure System → SonarQube servers:

SonarQube servers

and SonarQube scanner in Manage Jenkins → Global Tool Configuration → SonarQube Scanner:

SonarQube scanner

The name of the:

  • server must be the same as used in the withSonarQubeEnv (in my example it is equal to "SonarQube")
  • scanner tool must be the same as used in the tool (in my example it is equal to "SonarQubeScanner3")

You also have to check checkbox Enable injection of SonarQube server configuration as build environment variables.