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
Static code analysis of github repository #6
Comments
Sure, let's give it a try and see what happens. I've registered the project on Coverity. It says it will take 48 hours for the first scan to complete. |
When it works maybe it is good to note the static code analysis in the README.md. With the URL where people can register to view the results. |
Don't you need Travis-CI for Coverity Scan? https://scan.coverity.com/travis_ci |
Cool it is added to coverity scan: https://scan.coverity.com/projects/4838 |
Yeah, I just did a manual build without Travis-CI. I had to download their tools, build the code with them, then upload the results, and wait 48 hours for the project to be approved. It found two issues which you can see here: https://scan.coverity.com/projects/4838/view_defects Neither of them are bugs; they're just unnecessary checks. They are incorrect nonetheless so I fixed them 6364b5c. It was good to have another static analysis tool test the code, but I don't think I'll stick with it. Getting it to run was kind of an insane amount of setup to get a code analysis when compared to typing I'd like to set up the project for continuous integration someday, but it seems like too much maintenance right now for such a small project. As it is, the build system already builds and runs the code in various configurations, so I'm happy just running |
It would be nice to let the high quality static code analysis tool Coverity scan the repository for flaws.
https://scan.coverity.com/github
This also integrates with continues integration tool Travis.
The text was updated successfully, but these errors were encountered: