To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
PVS-Studio as a plugin for SonarQube

PVS-Studio as a plugin for SonarQube

Jun 16 2017

SonarQube is an open source platform, designed for continuous analysis and measurement of code quality. More than a year PVS-Studio has a plugin for the integrating the results of the work in SonarQube. Thanks to it, the abilities of detection critical errors in C/C++/C# can be expanded by the functionality of the quality monitoring. PVS-Studio and SonarQube greatly complement each other, allowing to build a powerful factory to bring the program code to the ideal state.

0513_PVS-Studio_and_SonarQube/image1.png

High-quality static analysis, in addition to the analysis itself, includes tasks of displaying the results of the work in the user-friendly format and providing a wide range of abilities to handle these results. Following these principles, PVS-Studio analyzer offers the following features:

  • Working with the bug report right in the tool window of Microsoft Visual Studio or a separate Standalone utility. Navigation along the code, filtering and sorting of the report, suppression of the display of certain warnings, particular files and folders are excluded from the analysis and so on.
  • The report file (xml) can be converted to a readable format (html, text) for further distribution among those who are interested.
  • The error list can be mailed to those developers who made the errors. To do this, there are special utilities built in PVS-Studio.
  • To accumulate the launch statistics and its further analysis in dynamics, there is a possibility to use a special tool Analysis Statistics, built into plugin for Microsoft Visual Studio or Standalone utility.

However, for the full management of the software project lifecycle, it's necessary to control not only errors, but also other metrics of the source code: the number of rows, cyclomatic complexity, amount of errors per KLOC, unit test code coverage, duplication and so on.

Despite the fact that PVS-Studio does not have built-in tools for continuous analysis and measurement of code quality, thanks to the possibility of integration with the SonarQube platform, all this is available to users of the Enterprise version of PVS-Studio already out of the box.

Using the PVS-Studio plugin for the integration of the C/C++/C# analysis results to SonarQube, in addition to the power of PVS-Studio, you get the following abilities:

  • Reports of code duplication, compliance with the coding standards, unit tests coverage, possible errors in the code, density of comments in the code, technical debt and much more.
  • Storing the history of metrics and building graphs for the changes of these metrics over time.
  • Fully automated analysis: integration with Maven, Ant, Gradle and common continuous integration systems.
  • Integration with such IDEs as Visual Studio, IntelliJ IDEA and Eclipse plugin using SonarLint.
  • Integration with external tools: JIRA, Mantis, LDAP, Fortify and so on.
  • Possibility of extending the existing functionality with the help of third-party plugins.
  • SQALE methodology to evaluate the technical debt.

Configuring of the SonarQube plugin won't take more than 15 minutes, after that you can load the analysis results to SonarQube using PVS-Studio and start using all the abilities of this tool, for example:

  • Advanced abilities of filtering, categorisation and sorting of warnings:
0513_PVS-Studio_and_SonarQube/image2.png

  • Code navigation:
0513_PVS-Studio_and_SonarQube/image3.png

  • Metrics and reports:
0513_PVS-Studio_and_SonarQube/image4.png

0513_PVS-Studio_and_SonarQube/image6.png

  • And much more ...

You can find the full list of SonarQube features on the official site. This article provides a detailed description of the integration of PVS-Studio into SonarQube.

Check your C/C++/C# projects using PVS-Studio analyzer, implement continuous analysis and management of your code using SonarQube plugin!

Download and try PVS-Studio: /en/pvs-studio/

An example of using PVS-Studio and SonarQube plugin in the analysis of PascalABC.NET is given in the article.

To purchase a commercial license, please contact us via the email. You can also write to us to get a temporary license key for a comprehensive investigation of PVS-Studio, if you want to avoid the limitations of the demo version.

Popular related articles
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept