-
Notifications
You must be signed in to change notification settings - Fork 2
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
More static code analysis in CI #62
Comments
In GitLab by @erreur404 on Jun 14, 2020, 14:03 Code Climage cannot be used because of antiagainst/codeclimate-cppcheck#33 |
Thanks for the info. That's good to know. Maybe we should then strive for making use of lgtm. Or are there other candidates? |
In GitLab by @erreur404 on Jun 14, 2020, 22:15 I know only coverity but i do not have the right to create project on the platform. I have also searched how to use lgtm but i found nothing for add opensource project. Maybe we need to contact her by mail. |
Coverity Scan has been setup now for KWinFT. Thanks @erreur404 for creating the project on this platform! I have now additionally setup a GitLab CI job in https://gitlab.com/kwinft/kwinft/-/merge_requests/32 to do regular nightly scans. Seems to work fine. With https://gitlab.com/kwinft/kwinft/-/merge_requests/29 landed we can check out tomorrow how the fixes affect the scan. We can do something similar for Wrapland of course but I believe KWinFT was the most important project to start with. Adding lgtm as a second service could be still a good idea. There is a help article about it working together with GitLab. One detail to note though is that the engine behind it was bought by Microsoft and that might indicate a focus on GitHub in the future. Still might work just fine on GitLab. |
The above mentioned Gitlab integration with Code Climate/cppcheck is still something we aim for. But at the moment cppcheck segfaults with some of our code. Backtrace provided by @tomenglund26:
This issue has been apparently already reported upstream (no link available to bug report right now though). |
Candidates:
Integration of clang-tools are separately tackled in #17. For code coverage tooling see #61.
The text was updated successfully, but these errors were encountered: