Manual analysis of C projects without a compile-commands.json

SonarQube Cloud
1

Hello everyone!

We are moving our repositories from Github to Gitlab and are stuck at migrating the sonarcloud analysis. Currently we use the automatic analysis for C and C++ projects, but this is not supported for Gitlab as far as we know. One of our repositories is a zephyr module containing a bunch of different C source files, acting as an sdk of sorts, where we can’t provide a compile-commands.json that would cover all (changed?) source files, instead we have a multiple small samples as part of our sdk.

What options do we have to get this working again?

2

Hi @dmalcorps,

C/C++ AutoConfig feature, which works independently of the DevOps platform, is already available on SonarQube Server. We’re working on bringing this functionality to SonarQube Cloud as well. However, we still have some pending work related to MISRA to complete first.

In the meantime, the only option is to provide a compile-commands.json file for analysis. :confused:

3

Hmmm… Any idea when that feature will be ready? This year? Next year? Next 5 years? A rough estimate maybe?

4

My best guess would be before the end of this year.