You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2016/12/15 03:03:58 UTC

[jira] [Commented] (THRIFT-3095) Enable CI Build for Coverity Scan integration

    [ https://issues.apache.org/jira/browse/THRIFT-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750226#comment-15750226 ] 

James E. King, III commented on THRIFT-3095:
--------------------------------------------

Having it done automatically would be ideal.

> 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: Build Process, Test Suite
>         Environment: Travis CI and Coverity Scan
>            Reporter: James E. King, III
>            Assignee: Roger Meier
>              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)