8000 Automate code analysis through Coverity scan by nulltoken · Pull Request #698 · libgit2/libgit2sharp · GitHub
[go: up one dir, main page]

Skip to content

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

Closed
wants to merge 1 commit into from
Closed

Conversation

nulltoken
Copy link
Member

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:

@nulltoken nulltoken closed this May 3, 2014
@nulltoken nulltoken deleted the coverity_scan branch May 3, 2014 21:21
@nulltoken nulltoken restored the coverity_scan branch May 3, 2014 21:21
@nulltoken nulltoken reopened this May 4, 2014
@nulltoken
Copy link
Member Author

Ok. So, I've came up with something.

This PR doesn't trigger the coverity Scan as triggers a standard build.
However, the coverity branch (which tracks the same commit) does (see the Travis logs).

So everything is more or less in place... except that it doesn't work. Yet.

The coverity tools outputs

[WARNING] No files were emitted. This may be due to a problem with your configuration
or because no files were actually compiled by your build command.
Please make sure you have configured the compilers actually used in the compilation.
 For more details, please look at: 
    /home/travis/build/libgit2/libgit2sharp/cov-int/build-log.txt
Extracting SCM data for 0 files...
Please see the log file '/home/travis/build/libgit2/libgit2sharp/cov-int/scm_log.txt' for warnings and SCM command issues.
Added 0 entries

/cc @dakshesh-coverity @daksheshvyas

@Therzok
Copy link
Member
Therzok commented Dec 8, 2014

Is there any way we can integrate coverity into AppVeyor? This would solve our issues with Coverity not working on Mono™.

@nulltoken
Copy link
Member Author

@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

@dakshesh-coverity
Copy link

Hi,

We have integration with Travis, which actually runs the script and performs the specific task.
Something similar can be done for AppVeyor.

Here is the script https://scan.coverity.com/scripts/travisci_build_coverity_scan.sh
It downloads the coverity build tool, run the build and upload it.

On Coverity Community someone has already explained about it in detail: https://communities.coverity.com/thread/3254

Thanks

Dakshesh Vyas | Technical Manager - Coverity Scan
Coverity | 185 Berry Street | Suite 6500, Lobby 3 | San Francisco, CA 94107
Office: 415.935.2957 | dvyas@coverity.commailto:dvyas@coverity.com
http://scan.coverity.com/
The Leader in Development Testing

From: nulltoken <notifications@github.commailto:notifications@github.com>
Reply-To: libgit2/libgit2sharp <reply@reply.github.commailto:reply@reply.github.com>
Date: Wednesday, December 10, 2014 at 1:47 AM
To: libgit2/libgit2sharp <libgit2sharp@noreply.github.commailto:libgit2sharp@noreply.github.com>
Cc: Dakshesh Vyas <dvyas@coverity.commailto:dvyas@coverity.com>
Subject: Re: [libgit2sharp] Automate code analysis through Coverity scan (#698)

@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.

@nulltoken
Copy link
Member Author

Superseded by #1078

@nulltoken nulltoken closed this Jun 9, 2015
@nulltoken nulltoken deleted the coverity_scan branch June 9, 2015 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0