기능

이 플러그인을 사용하면 Jenkins 글로벌 환경 설정에서 SonarQube 서버 환경을 설정할 수 있습니다.

이후 표준 Jenkins Build Step으로 SonarQube 분석을 다음 Scanner로 수행할 수 있습니다:

• SonarQube Scanner
• SonarQube Scanner for Maven
• SonarQube Scanner for MSBuild

Jenkins의 job이 완료되면, 이 플러그인 SoanrQube 분석 여부를 식별하고 job 페이지에  SonarQube  배지를 표시합니다. 해당 배지를 클릭하면 SonarQube 대시보드로 이동해 quality gate 상태를 확인할 수 있습니다.

SINCE 2.5 : Jenkins Pipeline DSL 도 사용할 수 있습니다(일부 기능은 SonarQube v6.2 이상에서만 동작합니다).

호환성 매트릭스

SINCE 2.5 JRE8 이상을 사용하여 분석해야 합니다

설치하기

1. Install the SonarQube Scanner for Jenkins via the Jenkins Update Center.
2. Configure your SonarQube server(s)
   1. Log into Jenkins as an administrator and go to Manage Jenkins > Configure System: 
   2. Scroll down to the SonarQube configuration section, click on Add SonarQube, and add the values you're prompted for.

사용하기

Analyzing with the SonarQube Scanner

Global Configuration

This step is mandatory if you want to trigger any of your SonarQube analyses with the SonarQube Scanner. You can define as many scanner instances as you wish. Then for each Jenkins job, you will be able to choose with which launcher to use to run the SonarQube analysis.

SonarQube Scanner를 사용해 SonarQube 분석을 수행하려면, 이 단계를 반드시 수행해야 합니다. 원하는 만큼의 스캐너를 설정한 뒤, 개별 Jenkins job에서 원하는 런처를 선택해 SonarQube 분석을 수행할 수 있습니다:

1. Jenkins에  administrator 계정으로 로그인 한 뒤, Manage Jenkins > Global Tool Configuration

1. 페이지로 이동합니다.
2. SonarQube Scanner 설정 영역으로 이동한 뒤, Add SonarQube Scanner

1. 를 클릭합니다. 기본적으로  Jenkins 도구를 자동설치하도록 설정되어 있습니다. 이미 설치한 Scanner를 선택하거나('Install automatically'

1. 체크 박스 해제) Jenkins가 특정 버전을 설치하도록 할 수 있습니다('Install automatically' 체크 박스 선택)

1. .

Jenkins가 업데이트 센터 파일을 다운로드하지 않은 경우(기본적으로 1일에 1회 다운로드)에는 사용 가능한 SonarQube Scanner 버전을 리스트에서 확인할 수 없을 수 있습니다. Manage Plugins > Advanced 탭에서 'Check Now' 버튼을 클릭해 강제로 업데이트 센터 파일을 다운로드 할 수 있습니다.

Job Configuration

1. Configure the project, and scroll down to the Build section. 
2. Add the SonarQube Scanner build step to your build.
3. Configure the SonarQube analysis properties. You can either point to an existing sonar-project.properties file or set the analysis properties directly in the Analysis properties field

Analyzing with SonarQube Scanner for MSBuild

Global Configuration

This step is mandatory if you want to trigger any of your analyses with the SonarQube Scanner for MSBuild. You can define as many scanner instances as you wish. Then for each Jenkins job, you will be able to choose with which launcher to use to run the SonarQube analysis.

1. Log into Jenkins as an administrator and go to Manage Jenkins > Global Tool Configuration

2. Click on Add SonarQube Scanner for MSBuild

3. Add an installation of the latest available version. Check Install automatically to have the SonarQube Scanner for MSBuild automatically provisioned on your Jenkins executors

   If you do not see any available version under Install from GitHub, first go to Manage Jenkins > Manage Plugins > Advanced and click on Check now

Job Configuration

1. Configure the project, and scroll down to the Build section.
2. Add both the SonarQube for MSBuild - Begin Analysis and SonarQube for MSBuild - End Analysis build steps to your build
3.  Configure the SonarQube Project Key, Name and Version in the SonarQube Scanner for MSBuild - Begin Analysis build step

4. Use the MSBuild build step or the Execute Windows batch command to execute the build with MSBuild 14 (see compatibility) between the Begin Analysis and End Analysis steps.
   Image Modified

Analyzing with SonarQube Scanner for Maven

Global Configuration

1. Log into Jenkins as an administrator and go to Manage Jenkins > Configure System
2. Scroll to the SonarQube servers section and check Enable injection of SonarQube server configuration as build environment variables

Job Configuration

1. Configure the project, and scroll down to the Build Environment section.

2. Enable Prepare SonarQube Scanner environment to allow the injection of SonarQube server values into this particular job. If multiple SonarQube instances are configured, you will be able to choose which one to use.

   Press the help button to learn which variables you can use in your build. Some values may be blank, depending on what was defined for the server.

   Image Modified

    

    

    

3. Once the environment variables are available, use them in a standard Maven build step by setting the Goals to include

   
   

   $SONAR_MAVEN_GOAL -Dsonar.host.url=$SONAR_HOST_URL

   
   

Analyzing in a Jenkins pipeline

Since version 2.5 of the SonarQube Scanner for Jenkins, there is an official support of Jenkins pipeline. We provide a 'withSonarQubeEnv' block that allow to select the SonarQube server you want to interact with. Connection details you have configured in Jenkins global configuration will be automatically passed to the scanner.

Here are a some examples for every scanner, assuming you run on Unix slaves and you have configured a server named 'My SonarQube Server' as well as required tools. If you run on Windows slaves, just replace 'sh' by 'bat'.

SonarQube Scanner

SonarQube Scanner for Gradle

SonarQube Scanner for Maven

SonarQube Scanner for MSBuild

Pause pipeline until quality gate is computed

The waitForQualityGate step will pause the pipeline until SonarQube analysis is completed and returns quality gate status.

Pre-requisites:

• SonarQube server 6.2+ (need webhook feature)
• Configure a webhook in your SonarQube server pointing to <your Jenkins instance>/sonarqube-webhook/  The trailing slash is mandatory with SonarQube 6.2 and 6.3!

• Use withSonarQubeEnv step in your pipeline (so that SonarQube taskId is correctly attached to the pipeline context).

Example:

SonarQube Scanner for MSBuild

Thanks to the webhook, the step is implemented in a very lightweight way: no need to occupy a node, and it doesn't prevent Jenkins to restart (step will be restored after restart).