|
ℹ️
|
This simple example ignores analysis cache and multithreaded execution both of which can boost analysis significantly. |
It is very easy to analyze a C, C++ and Objective-C project with SonarQube in your Jenkins Pipelines:
-
Create a
sonar-project.propertiesfile to store your configuration -
Follow the steps described in the documentation of SonarScanner for Jenkins
-
Install and configure the "SonarQube Scanner for Jenkins" plugin in "Configure System" section
-
Configure the SonarScanner in "Global Tool Configuration" section
-
-
Add a task to download the Build Wrapper
-
Wrap your compilation with the Build Wrapper
-
Launch the analysis using
withSonarQubeEnvblock
You can take a look at the sonar-project.properties and Jenkinsfile to see it in practice. Please be aware that the SonarQube server URL is not completed in this Jenkinsfile example.
A build of the code repository on a Linux platform using CMake build system.
To build the code run:
mkdir build && cd build cmake .. make
An example of a flawed C++ code. The code repository is meant to be compiled with different build systems using different CI pipelines on Linux, MacOS, and Windows.
The code repository is forked into other repositories in this collection to add a specific build system, platform, and CI. The downstream repositories are analyzed either with SonarQube or SonarCloud.
You can find examples for:
Using the following build systems:
Running on the following CI services:
-
Additionally, generic examples demonstrate integration with other CIs and manual-configuration examples should help you if you are running locally.
Configured for analysis on:
You can find also a few examples demonstrating:
See examples-structure.adoc for a description of the structure of this GitHub organization and the relations between its different repositories.