-
Notifications
You must be signed in to change notification settings - Fork 899
Automate code analysis through Coverity scan #698
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
Conversation
Ok. So, I've came up with something. This PR doesn't trigger the coverity Scan as triggers a standard build. So everything is more or less in place... except that it doesn't work. Yet. The coverity tools outputs
|
Is there any way we can integrate coverity into AppVeyor? This would solve our issues with Coverity not working on Mono™. |
@Therzok Nice idea! However, AFAIK, there's no direct integration with the two services. So we would have to do this by hand. We could get some inspiration from @ben's work on libgit2/coverity and port it to PowerShell. One thing to keep in mind though: AppVeyors builds are limited to 30min runs. Once this is reached, the build is force timed out. Thus, we should make sure that the whole coverity process (download/analyze/upload) doesn't take more than 15/20 mins. /cc @FeodorFitsner |
Hi, We have integration with Travis, which actually runs the script and performs the specific task. Here is the script https://scan.coverity.com/scripts/travisci_build_coverity_scan.sh On Coverity Community someone has already explained about it in detail: https://communities.coverity.com/thread/3254 Thanks Dakshesh Vyas | Technical Manager - Coverity Scan From: nulltoken <notifications@github.commailto:notifications@github.com> @Therzokhttps://github.com/Therzok Nice idea! However, AFAIK, there's no direct integration with the two services. So we would have to do this by hand. We could get some inspiration from @benhttps://github.com/ben's work on libgit2/coverityhttps://github.com/libgit2/libgit2/blob/master/script/coverity.sh and port it to PowerShell. One thing to keep in mind though: AppVeyors builds are limited to 30min runs. Once this is reached, the build is force timed out. Thus, we should make sure that the whole coverity process (download/analyze/upload) doesn't take more than 15/20 mins. /cc @feodorfitsnerhttps://github.com/feodorfitsner Reply to this email directly or view it on GitHubhttps://github.com//pull/698#issuecomment-66426929. |
Superseded by #1078 |
Coverity Scan now supports C# in Beta. Might be interesting to leverage this analysis as part of our CI build.
The project has been registered but isn't fully configured yet.
Some potential references: