News and Notes from the Makers of Nexus | Sonatype Blog

Continuous integration in pipeline as code environment with Jenkins, JaCoCo, Nexus, and SonarQube

Written by Rahul Vishwakarma | January 17, 2018

Here we discuss the setup for a Continuous integration pipeline. This is for Mavenized Spring boot build with JaCoCo coverage reports and Sonar metrics. I used a windows machine with Tomcat 8 for hosting Jenkins, but similar setup can be done on any OS where Sonar server can run on the same system.

A. Get the following artifacts on the system

  1. Tomcat server with Java JDK – Configure the server.xml to run on port 8099

  2. Setup Maven and other build utilities on your machine

  3. Access to GitHub source code

  4. Source code should have the Jenkinsfile in project root to be used by the pipeline

  5. Source should have the sonar-project.properties in project root for the SonarQube project linkage & source paths

B. Setup and startup SonarQube

  1. Download the SonarQube package from https://www.sonarqube.org/#downloads

  2. Start sonar server: SONAR_HOME\bin\windows-x86-32\StartSonar.bat (for 32 bit Windows)

  3. Open Sonar admin page "http://localhost:9000". Default credentials – admin/admin

  4. Create user in security tab and generate an access token, 50997f4a8c26d5698cccee30cf398c0ed9b98de0

  5. Create a project SPRINGBOOT with a key

  6. Download SonarQube scanner from https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner

  7. Additional configuration from https://docs.sonarqube.org/display/SCAN/Advanced+SonarQube+Scanner+Usages

C. Setup and startup Tomcat

  1. Download jenkins.war from https://jenkins.io/download

  2. Put the jenkins.war file in webapps folder of Tomcat home

  3. Set Environment Variables as follows,

  4. SET JENKINS_HOME=”C:/Users/vishwaka/Documents/Workspace/git/jenkinstest/cisetup/jenkins_home”

  5. SET CATALINA_OPTS=”-DJENKINS_HOME=C:/Users/vishwaka/Documents/Workspace/git/jenkinstest/cisetup/jenkins_home”

  6. Start the server using startup.bat

D. Initialize Jenkins

  1. Access Jenkins at http://localhost:8099/jenkins

  2. Provide the initial credentials from jenkins_home/secrets/initialPassword*

  3. Install the default set of plugins and proceed

  4. Create a user for this installation

  5. Use "New Item" for creating a pipeline and provide the Jenkinsfile pipeline script from Git SCM for this

E. Plugin and configuration to Jenkins

  1. Add the "JaCoCo plugin" through the Manage Jenkins > Manage Plugins and install without restart

  2. Add "SonarQube Scanner for Jenkins" through the same Plugin Manager as above

  3. Go to the Manage Jenkins > Configure system and provide the credentials for Sonar Server

  4. Add the "SonarQube Server" name running on URL http://localhost:9000 alongwith user authentication key generated in SonarQube Server user administration page

  5. Remove the auto install option and add the "Sonar Scanner" env variable SONAR_RUNNER_HOME installation path as $JENKINS_HOME/sonar-scanner-3.0.3.778-windows through "Global Tool Configuration"

  6. Make sure the Sonar scanner path is configured properly as its path is hard coded in Jenkinsfile.

F. Run the build now for this pipeline

  1. The pipeline is at http://localhost:8099/jenkins/job/JENKINS-BOOT/

2. Checkout the coverage report within the pipeline reports

3. You can also look at the Sonar reports at http://localhost:9000/dashboard?id=JENKINSBOOT

4. If you have many such projects then its better to execute all your Job Pipelines from a parent Job Pipeline. You can create one and call it "BUILD-ALL-JOBS". It can be configured using the below pipeline script to run your JENKINS-BOOT job described in the example above as well as any other fictitious job call JENKINS-BOOT-XXX.

node {
    stage('JENKINS-BOOT-STAGE-A') {
        build job: 'JENKINS-BOOT'
    }
    stage('JENKINS-BOOT-STAGE-B') {
        build job: 'JENKINS-BOOT-XXX'
    }
}

There are plugins to build jobs in parallel as well but that depends on what workflow you want to build in your system.

G. Adding Nexus repository management capability to your CI environment from my blog

Click on the text link below:

Repository Management with Nexus 3 for your Mavenized project, including release and snapshot distribution

H. Finally put everything into a script that can run it all

Pardon my naive and careless script, considering my setup is on a local windows development workstation.

@echo off
echo "--------------------------------------------------------------------------"
echo "------------------------- CI STARTUP SCRIPT ------------------------------"
echo "--------------------------------------------------------------------------"

echo "Startup SonarQube Server"
echo "------------------------"
START CMD /C "cd c:\Dock\ci\sonar\sonarqube-6.4\bin\windows-x86-64 & CALL StartSonar.bat"
echo "Sonar may be up on http://localhost:9000/"

echo "Startup Nexus Repository Manager"
echo "--------------------------------"
START CMD /C "cd c:\Dock\ci\nexus\nexus-3.3.1-01\bin & nexus.exe /run"
echo "Nexus may be up on http://localhost:8081/"

echo "Startup Jenkins on Tomcat"
echo "-------------------------"
START CMD /C "cd c:\Dock\ci\jenkins\apache-tomcat-8.5.15\bin & startup.bat"
echo "Jenkins may be up on http://localhost:8099/jenkins"

echo "-------------------------------- END -------------------------------------"

About Rahul Vishwakarma

Strong application design and development skills in the area of cloud, analytics and Internet-of-Things initiatives. Oriented on design, development and management of big data, public cloud and connected devices ecosystem. I love problem statements, and the best times are spent brainstorming for their solutions.

Heading towards Machine Vision and connected research areas on signals.

Resources for this article
View full post