Achieving Continuous Code Quality with SonarQube and Jenkins


In the world of software development, maintaining high code quality is crucial for long-term success. Low quality code leads to technical debt, reduces maintainability and makes the system prone to bugs. To avoid these pitfalls, developers need to continuously inspect code quality and take corrective actions. This is where the powerful combination of SonarQube and Jenkins comes in.

SonarQube is an open source platform for continuous inspection of code quality. It can detect code smells bugs vulnerabilities and other issues in over 25 programming languages including Java, C#, JavaScript, C/C++, Python and more.

Jenkins is the leading open source automation server It allows automating software development processes like build, test, and deployment Jenkins has great plugin support and can easily integrate with other tools via its REST API.

Together, SonarQube and Jenkins enable automating code quality analysis as part of the continuous integration/continuous delivery (CI/CD) pipeline. Developers can get rapid feedback on new code before it gets merged. This prevents accumulation of technical debt and results in higher code quality over time.

In this article we will explore how to setup SonarQube analysis in Jenkins to track code quality metrics detect issues and enforce quality gates.

Key Benefits of Integrating SonarQube with Jenkins

Here are some major benefits you can realize by integrating SonarQube and Jenkins:

  • Get detailed code quality reports within Jenkins on key metrics like bugs, vulnerability count, code smells, duplication etc.

  • Configure Jenkins jobs to automatically run SonarQube analysis on code changes and reject builds breaking quality thresholds.

  • Track quality metrics over time and enable early detection of quality erosion through continuous inspection.

  • Support code reviews by providing SonarQube findings alongside pull requests. Reviewers can verify quality before merging PRs.

  • Enforce coding best practices by setting up SonarQube quality profiles based on organization’s standards.

  • Support large-scale analysis of complex codebases involving hundreds of projects and millions of lines of code.

  • Leverage the dozens of plugins shared between Jenkins and SonarQube for further integrations.

Step-by-Step Setup Guide

Follow these steps to get started with SonarQube code quality management in Jenkins:

1. Install and Setup SonarQube Server

Download the latest SonarQube Server edition from It comes as a standard .zip archive.

Unzip it on your desired server machine. The sonarqube-x.y directory contains all SonarQube files.

For simple testing, you can directly launch the SonarQube Server by running .binwindows-x86-xxStartSonar.bat on Windows or ./bin/linux-x86-64/ start on Linux.

For production usage, configure SonarQube as a service so it starts automatically on system boot.

2. Install and Configure SonarScanner

SonarScanner is the analysis tool that runs static code analysis and sends data to SonarQube server. Install it on build agent machines or integrate it with your CI/CD pipeline.

Download the latest scanner ZIP from

Configure with the right settings:

3. Install SonarQube Plugin on Jenkins

On your Jenkins server, go to Manage Jenkins → Manage Plugins and search for SonarQube plugin. Install it and restart Jenkins.

Alternatively, in script console use: --install sonar

This will let you configure SonarQube servers and use the integration features.

4. Configure SonarQube Server in Jenkins

Under Manage Jenkins → Configure System → SonarQube servers:

  • Add a new SonarQube server using the URL: http://your-sonarqube-server:port

  • Under credentials, add a secret text credential with the authentication token from SonarQube.

5. Create a Jenkins Pipeline Job

Under New Item, create a new Pipeline job. Under build steps, add a SonarQube Scanner step and configure:

  • SonarQube server selected in previous step
  • Analysis properties like sonar.projectKey, sonar.sources etc.

This will run SonarQube analysis as part of the build.

You can also run analysis via standard Jenkins tools or using the SonarScanner tool directly.

6. Configure Quality Gates

Under Quality Gates in SonarQube, you can define quality thresholds like maximum blocker issues, minimum test coverage etc.

In your Jenkins job, add a Wait for Quality Gate step after analysis. This will pause the build until the quality gate passes or fail the build otherwise.

7. View Detailed Code Quality Reports

After the analysis runs, go to the project dashboard in SonarQube to see detailed code quality reports.

Similarly, SonarQube analysis results will also be visible in the build overview page in Jenkins.

This completes the integration. You can now get rapid feedback on code quality issues directly in Jenkins. Over time, you can analyze trends, optimize quality gates and meetings business goals.

Key Integration Features

Some other key features provided by the Jenkins – SonarQube integration are:

  • Ability to trigger analysis on other connected SonarQube servers remotely.

  • Inline comments on PRs showing SonarQube issues using the Analysis Report plugin.

  • Code coverage metrics and reports for unit tests.

  • Integration with LDAP for unified user management between SonarQube and Jenkins.

  • Notifications about quality gate status via emails or on collaboration platforms like Slack and Microsoft Teams.

Using SonarQube and Jenkins together enables automation of code quality management alongside your CI/CD pipelines. Developers get rapid feedback through every stage – commit, pull request, build, test etc.

Setting up quality gates ensures that only clean, high quality code gets deployed to production. This prevents accumulation of technical debt, reduces maintenance costs and results in more robust systems with lesser bugs.

To summarize, integrating SonarQube analysis in Jenkins improves developer productivity, reduces risks and costs, and sets up processes for engineering high quality code. It is a must-have toolchain for any serious software engineering team.

defined in Jenkins
you will need to add build step to execute the analysis passing on required properties.

Tell me about the Jenkins Build Pipeline plugin. How can you use Jenkins Build Pipeline plugin to visualize your pipeline?

The Jenkins Build Pipeline plugin is a powerful tool that adds an extra layer of visibility and management over your Jenkins projects. When dealing with a complex project with multiple stages
or jobs
visualizing and managing the complete flow can become challenging. This is where the Build Pipeline plugin comes in.

The Build Pipeline plugin allows you to create a visual representation of your projects build pipeline. This representation allows you to:

Visualize the project build flow: The plugin displays a series of connected tasks (the pipeline) and shows progress

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *