C++ example project scanned on SonarCloud using Bitbucket Cloud pipelines

To analyze a C, C++ and Objective-C project on Bitbucket pipelines with SonarCloud, follow the steps described here: Getting started with Bitbucket Cloud.

To sum up, you need to:

1. Enable pipelines in your Bitbucket Cloud repository

2. Add a repository variable SONAR_TOKEN with the value given by SonarCloud during the setup

3. In your bitbucket-pipelines.yml file:

   1. Download the build wrapper and wrap your compilation with it

   2. Download and launch sonar-scanner

You can take a look at the sonar-project.properties and bitbucket-pipelines.yml to see it in practice.

Documentation

• Documentation of the C, C++ and Objective-C plugin and its Build Wrapper

• Bitbucket Cloud Integration

• Analyze your repository with Bitbucket Pipelines

• Configuring C, C++ and Objective-C analysis cache

• Configuring multithreaded execution

• Using compilation database (compile_commands.json)

Linux\Autotools

A build of the code repository on a Linux platform using GNU Autotools build system.

To build the code run:

autoreconf --install
./configure
make clean all

Code Description

An example of a flawed C++ code. The code repository can be analyzed automatically, but it can also 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:

• Linux

• macOS

• Windows

Using the following build systems:

• CMake

• GNU Autotools

• Xcode

• MSBuild

Running on the following CI services:

• Azure DevOps

• GitHub Actions

• Travis

• Jenkins

• GitLab CI

• BitBucket Pipelines

• Additionally, generic examples demonstrate integration with other CIs and manual-configuration examples should help you if you are running locally.

Configured for analysis on:

• SonarQube

• SonarCloud

You can find also a few examples demonstrating:

• The use of Compilation Database (compile_commands.json)

• Test coverage

See examples-structure.adoc for a description of the structure of this GitHub organization and the relations between its different repositories.