About the documentation, can you please tell me what you feel is missing if you read the pointed SonarCloud C++ analysis documentation?
I did mention some points in another thread but:
- Usage of
sonar.projectVersionis confusing. From another thread it seems that you should not change it for PRs, tag pushes, etc. - The build wrapper is still a black-box, and it is unclear how it differs with compilation-database. The
Reasons to use ...should be a table showing what is processed by each method, e.g. environment variables, defines, cmake configurations, etc. - It is unclear if the wrapper works on the level of compiler (
gcc), generator (ninja), and/or build backend (cmake) - If there are missing metadata, how can we add them, e.g. if we want the static analyzer to report on various OS, toolchains, build variants, etc.
- How to decouple the testing/code-coverage so that in the Github workflow we can better schedule and re-use artifacts