-
Notifications
You must be signed in to change notification settings - Fork 34
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When looking quickly through sonarcloud documentation (https://docs.sonarqube.org/display/PLUG/Building+on+Linux), it seems we must to run build-wrapper-linux-x86-64 before sonar-scanner for C++ projects.
I saw somewhere this could avoid some false positives.
There is a project referenced by https://github.com/SonarSource/sonarcloud_examples with a C++ example where they run build-wrapper-linux-x86-64 before executing sonar-scanner: https://github.com/SonarSource/sq-com_example_c-sqscanner-travis/blob/master/.travis.yml
@bourtemb , yes, you are absolutely right! That would be further improvement. We just need to figure out how to integrate build-wrapper into our dockers (which BTW would be nice to replace with native Travis images if possible). Anyway at this point it is already a good result, and I like the result of the analysis. |
I understand... |
32693f2
to
f66e560
Compare
SonarCube hosted on sonarcloud.io seems to be much better alternative(addition) to codacy.
Result of the analysis of this branch can be found here