Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 072E4200D0F for ; Thu, 14 Sep 2017 21:47:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 06BEB1609C6; Thu, 14 Sep 2017 19:47:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 568A71609CD for ; Thu, 14 Sep 2017 21:47:05 +0200 (CEST) Received: (qmail 95367 invoked by uid 500); 14 Sep 2017 19:47:04 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 95348 invoked by uid 99); 14 Sep 2017 19:47:04 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Sep 2017 19:47:04 +0000 Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id A04371A0019 for ; Thu, 14 Sep 2017 19:47:03 +0000 (UTC) Received: by mail-io0-f176.google.com with SMTP id e189so3329743ioa.4 for ; Thu, 14 Sep 2017 12:47:02 -0700 (PDT) X-Gm-Message-State: AHPjjUizTm8M6H35v4IYLDBzm0EYn13x7LVGCq67tYT0xv9soMTDbaA1 gl3SwxMJPUFH0oxRjHRWQXp4VEidJ3tryEGuPk0WFg== X-Google-Smtp-Source: AOwi7QArRhWTdj41LdWGR/G7m9IAl0FQ94YvFsERPN/tK7KY4XAeYP4X4dIarTl5ygwX+T1KL9Cco1O9i2R+wBiP1Gc= X-Received: by 10.107.142.72 with SMTP id q69mr2618142iod.58.1505418421525; Thu, 14 Sep 2017 12:47:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.34.129 with HTTP; Thu, 14 Sep 2017 12:46:20 -0700 (PDT) In-Reply-To: References: From: Dmitriy Setrakyan Date: Thu, 14 Sep 2017 12:46:21 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Static code analysis for Java To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c05edd2410f6505592b8a22" archived-at: Thu, 14 Sep 2017 19:47:06 -0000 --94eb2c05edd2410f6505592b8a22 Content-Type: text/plain; charset="UTF-8" Hm... LGTM tool looks nice! Check out all the errors it already found in Ignite :) https://lgtm.com/projects/g/apache/ignite/alerts/?mode=list&severity=error D. On Thu, Sep 14, 2017 at 9:21 AM, Pavel Tupitsyn wrote: > Yes, we can run IDEA inspections, and this is the simplest thing to do, > since TeamCity already has this step available. > > On Thu, Sep 14, 2017 at 7:05 PM, Alexey Kuznetsov > wrote: > > > AFIK, we can run on TC same code analyzer that built in IDEA. > > > > See: > > > > CodeCoverageResults > > > > https://confluence.jetbrains.com/display/TCD10/Working+ > with+Build+Results# > > WorkingwithBuildResults-CodeCoverageResults > > > > Code Inspection > > > > https://confluence.jetbrains.com/display/TCD10/Working+ > with+Build+Results# > > WorkingwithBuildResults-CodeInspectionResults > > > > On Thu, Sep 14, 2017 at 10:28 PM, Anton Vinogradov < > > avinogradov@gridgain.com > > > wrote: > > > > > Wow, > > > Seems, that's what we were looking for! > > > > > > On Thu, Sep 14, 2017 at 6:26 PM, Malcolm Taylor > > > wrote: > > > > > > > Yakov, > > > > > > > > You might also wish to consider lgtm.com, which is already analysing > > > > Ignite > > > > builds ( https://lgtm.com/projects/g/apache/ignite/ ). > > > > It has found a number of issues, some of which have been fixed > through > > > > https://issues.apache.org/jira/browse/IGNITE-5805 > > > > lgtm also supports the option of GitHub integration as discussed in > > > > https://lgtm.com/docs/lgtm/using-lgtm-analysis- > continuous-integration > > > > > > > > Regards, > > > > > > > > Malcolm > > > > > > > > On 14 September 2017 at 16:02, Yakov Zhdanov > > > wrote: > > > > > > > > > Guys, > > > > > > > > > > I remember we tried some static code analysis tools for Java (a bit > > > > awkward > > > > > not having one yet), but we did not setup regular checks. > > > > > > > > > > I want to return to this. As result I would like to have code > > analysis > > > > tool > > > > > running on TC on daily basis and also established process to review > > and > > > > fix > > > > > code based on tool report same as we do with failed tests. > > > > > > > > > > So, I consider several options: > > > > > > > > > > 1. Findbugs - simple, free, runs locally, seems to have report > parser > > > in > > > > TC > > > > > and maven plugin > > > > > 2. https://www.sonarqube.org/ - free, runs locally and user > uploads > > > info > > > > > to > > > > > Sonarqube server for analysis, has very basic TC plugin that > uploads > > > > bundle > > > > > to server and links build results on TC to results at Sonarqube > site. > > > > > 3. https://scan.coverity.com/projects/apache-ignite - Coverity > seems > > > to > > > > be > > > > > very powerful, free for opensource, runs locally and then user > > uploads > > > > > results to server for analysis. > > > > > > > > > > Anton Vinogradov, can we try setting up Findbugs on TC and see how > it > > > > works > > > > > and integrates with TC? As it seems to be the most simple option to > > get > > > > > results faster. > > > > > > > > > > Then we can compare it to Coverity and take decision what to do > next. > > > > > > > > > > --Yakov > > > > > > > > > > > > > > > > > > > > -- > > Alexey Kuznetsov > > > --94eb2c05edd2410f6505592b8a22--