-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parse Clang Static Analyzer plist reports #1161
Conversation
@gyorb thanks for your contribution. We will review it... |
@wichtounet think that's the feature you were looking for. Maybe you have also some time to try it out... |
Hi, Thanks for this contribution 👍 I just installed this on my sonar instance and try to test it. But I seen one big problem. Unless I'm mistaken, you have to set the path of a single plist file, right ? How do you to handle the use of scan-build ? scan-build generates a set of plist files in a folder. If you don't plan to support scan-build, could you tell me how to use the static-analyzer with several threads? Thanks :) |
Hi, I've tested the plugin with scan-build and it can parse multiple plist files. The trick is to configure an ant-style glob pattern as a reportPath like this: I've used this scan-build and Clang v3.8 for testing. I wanted to create a wiki section on how to analyze a project and import the results, after the new feature is accepted. I found a SampleProject2 should I update the documentation there too? |
Ok, perfect. I didn't think of trying that. I used:
And it worked well. I tested the official scan-build only. It had to force alpha checkers to find issues in my programs. The analysis worked fine and the three warnings from the clang-static-analyzer were correctly reported in Sonar. For me, it seems to work quite well. I don't have projects with lots of violations of static-analyzer, so cannot really test with large number of errors . |
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.
@gyorb looks good to me. Think two additional things are missing:
- add documentation in wiki
- add an integration sample
integration test:
|
@gyorb do you work on integration test or should we merge it as is? |
@guwirth I had some other things to do and I did not finish the integration tests yet. I hope I can finish them soon. |
@gyorb I merge this so other has the chance to try it. |
@gyorb thx for providing detailed documentation how to use the feature. |
Add support to parse Clang Static Analyzer plist results:
Resolves #547
This change is