[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kdepimlibs Coverity Scan Report, Oct 14 2014
From:       Gilles Caulier <caulier.gilles () gmail ! com>
Date:       2014-10-16 13:06:33
Message-ID: CAHFG6sHYibQDPWjwkireYWZty8UpRLeRCR67=8naz4Q6uKN21A () mail ! gmail ! com
[Download RAW message or body]

2014-10-16 12:29 GMT+02:00 Ben Cooksley <bcooksley@kde.org>:
> On Thu, Oct 16, 2014 at 8:53 PM, Gilles Caulier
> <caulier.gilles@gmail.com> wrote:
>> Allen,
>
> Hi Gilles,
>
>>
>> Just a workflow question : why to export Coverity report to CSV where
>> you can send automatically a mail to devel mailing list when scan is
>> complete, with a a list of new defect found in code.
>>
>> I use Coverity since more than one year with whole digiKam code, and
>> we have already fixed more than 500 entries detected. The Coverity web
>> interface is really more suitable than a export to CSV. Defect are
>> very well explained in source context, with all conditions used to
>> check implementation.
>>
>> The only constrain is to have an account for each contributors who
>> will fixed entries.
>
> I suspect that is why Allen is sending out the HTML/CSV output -
> because not everyone has access and it is helpful to have this
> information publicly accessible.

All is configurable in Coverity interface. You can invite people and
attribute role.

Web interface is so far more powerful to use than CSV, and permit a
time gain to fix issues.

Gilles Caulier
[prev in list] [next in list] [prev in thread] [next in thread]