[ https://issues.apache.org/jira/browse/THRIFT-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526635#comment-14526635 ]
James E. King, III edited comment on THRIFT-3095 at 5/4/15 1:43 PM: -------------------------------------------------------------------- I believe Roger did this work in the past, assigning to him. The Coverity Scan project was updated recently and the results need to be examined - I had started in on this and getting rid of the false positives, etc. was (Author: jking3): I believe Roger did this work in the past, assigning to him. The Coverity Scan project was updated recently and the results need to be examined. > Enable CI Build for Coverity Scan integration > --------------------------------------------- > > Key: THRIFT-3095 > URL: https://issues.apache.org/jira/browse/THRIFT-3095 > Project: Thrift > Issue Type: Improvement > Components: C# - Compiler, C# - Library, C++ - Compiler, C++ - > Library, Java - Compiler, Java - Library > Environment: Travis CI and Coverity Scan > Reporter: James E. King, III > Labels: Coverity, StaticCodeAnalysis > > Coverity offers a wonderful free static code analysis tool for C++, C# and > Java open source projects. It is very easy to automate submissions to > Coverity Scan for code analysis - I just spent about 15 minutes today (not > including build time) setting up the GNU C Library (glibc) in Coverity Scan. > We should create a CI job that submits results to Coverity Scan to improve > the overall quality of the codebase. This is a low-effort, high-reward > improvement. > If you want to see why this is so powerful please review the Coverity Scan > project for the GNU C Library (glibc), something we all use every day: > https://scan.coverity.com/projects/4826?tab=overview -- This message was sent by Atlassian JIRA (v6.3.4#6332)