Hello SonarQube Server users!
We want to inform you that we will be soon releasing a new minor version (v2.1.0
) of our GitHub action for C, C++, and Objective-C with SonarQube Server (sonarqube-github-c-cpp
).
DEPRECATION WARNING
This new version of the GitHub action for C, C++, and Objective-C with SonarQube Server (sonarqube-github-c-cpp
) is going to be the last one specifically designed for these languages.
The action is now deprecated and will be removed in a future release.
Since v4.2
, the GitHub action for SonarQube (sonarqube-scan-action
) supports C, C++, and Objective-C, and is the unique entrypoint to SonarQube Server and Cloud!
The unified action fixes issues with SSL certificates and brings new features, such as the possibility of specifying the Sonar Scanner CLI version. You can read more in this community post and in the README of the action.
Migration instructions
If the action is used to install both the SonarScanner CLI and the Build Wrapper:
- replace
sonarqube-github-c-cpp
with the latest version ofSonarSource/sonarqube-scan-action/install-build-wrapper
- if the step calling the action is named
Install sonar-scanner and build-wrapper
, or something similar, rename it toInstall Build Wrapper
- replace the step calling
sonar-scanner
with a step usingSonarSource/sonarqube-scan-action
- the arguments passed to
sonar-scanner
should be passed to the action via theargs
input parameter
If the action is used to install the SonarScanner CLI, and the Build Wrapper is not required:
- remove the
sonarqube-github-c-cpp
step altogether - replace the step calling sonar-scanner with a step using
SonarSource/sonarqube-scan-action
- the arguments passed to sonar-scanner should be passed to the action via the
args
input parameter
Check the C++ section in the README of the sonarqube-scan-action
, as well as
sample C and C++ projects with SonarQube Server analysis configured for complete and fully working examples.
Notice that, if you update to sonarqube-github-c-cpp@v2.1.0
, you will receive warnings in logs and annotations encouraging you to move to the latest version of sonarqube-scan-action
.
You may already have noticed the warnings above if you are using sonarqube-github-c-cpp@master
instead of a specific version (which we don’t recommend doing, unless you want to always automatically be on the latest version, at the risk of occasionally breaking your pipeline).
We don’t expect any issue migrating and we encourage you to move to sonarqube-scan-action@v4
. Should you encounter any issues, don’t hesitate to create a new post here in the community describing your scenario and providing logs.
Best regards,
Antonio