DevOps Integration

Build Systems

For dynamic languages like JavaScript, PHP, Python, … executing an analysis is as easy as feeding SonarQube with a bunch of source files. But for languages like Java, C#, C, C++ and Objective-C, there is simply no way to provide accurate results without being part of the build. That’s why built-in integrations are provided for MSBuild, Maven, Gradle, Ant, and Makefiles.

build systems

ci engines

CI Engines

Native integrations with build systems let you easily schedule the execution of an analysis from all CI engines: Jenkins, Azure DevOps (formerly VSTS/TFS), Travis-CI… Don’t worry if your CI engine isn’t listed here, integration effort will be minimum.

Pass/Fail Notification

Once an analysis is done, a report is sent to the SonarQube server to be integrated. At the end of this integration, a standard webhook mechanism lets you notify any external system to do whatever you want: trigger an alarm, update a wallboard, notify a chat room.

notifications quality gate

full web api

Full Web API

As part of the overall development ecosystem, the SonarQube Web API can be used to automatically provision a SonarQube project, feed a BI tool, monitor SonarQube, etc. Morever the list and definition of all the Web API is built in SonarQube.

Promotion Pipelines

Using webhooks, SonarQube can be integrated as a promotion step in your delivery pipelines. This way, you can make sure that only artifacts that pass the Quality Gate will be released and deployed to production.

quality gate

High Availability

High Availability

Ensure maximum uptime code quality services for distributed global developer teams and high-volume projects. Test hundreds of millions of lines of code across multiple locations and teams without worrying about downtime or interruption.