Clang-Tidy: handle clang warnings in the report file (-W) #2803
Conversation
|
@cmorve-te thanks! I run first CI before I' looking into it ... |
|
@cmorve-te checks of CI are green, will do a code review next.
Why do you wanna have it in version 2.1? The version 2.2 is also supporting SQ 9.9 LTS and SQ 10 ... |
Looking at https://github.com/SonarOpenCommunity/sonar-cxx/wiki/Compatibility-Matrix I though 2.2 would not support 9.9. If it does, ignore it, I don't care about 2.1. |
@cmorve-te In the last releases we were always supporting the current and last LTS, but this depends on the API compatibility. Currently we test the 2.2 in our CI with SQ 9.9 LTS and the latest 10.x (and currently it's working). Hope SonarSource will not do any breaking changes. |
|
I updated the compatibility matrix and beta release notes. |
guwirth
changed the title
guwirth
changed the title
There was a problem hiding this comment.
@cmorve-te thanks for providing this, I will merge it. Think the Clang-Tidy parser needs some general refactoring I will do afterwards.
Extend the existing Clang-Tidy sensor to also understand clang compiler issues (
[-W...]) in the LOG files and map them to clang-tidy rules ([clang-diagnostic-...]). Clang compiler issues would be visualized in the SQ UI as Clang-Tidy issues (as per #2325 (comment)).Sample:
[-Wunneeded-internal-declaration][clang-diagnostic-unneeded-internal-declaration][-W...]=>[clang-diagnostic-...]close #2325
This change is