12:37 a.m.
I see the github project ovirt-engine (https://github.com/oVirt/ovirt-engine) is
registered on Coverity Scan for routine analysis
(https://scan.coverity.com/projects/ovirt-engine?tab=project_settings).
My question is -
1) do we only build and analyze the master branch on Coverity?
1a) If yes, why do we not analyze the other branches?
1:49 p.m.
New subject: Is only master branch of ovirt-engine analyzed on coverity scan?
On Wed, Mar 20, 2019 at 10:38 PM <simtiaz(a)ncsu.edu> wrote:
I see the github project ovirt-engine (
https://github.com/oVirt/ovirt-engine) is registered on Coverity Scan for
routine analysis (
https://scan.coverity.com/projects/ovirt-engine?tab=project_settings).
My question is -
1) do we only build and analyze the master branch on Coverity?
Yes
1a) If yes, why do we not analyze the other branches?
Every patch needs to be merged to master before backport any stable release
branch, so it wouldn't add too much value to perform coverity scan also on
stable branches
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/V5XEPILH4NZ...
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
8:06 p.m.
New subject: Is only master branch of ovirt-engine analyzed on coverity scan?
Il gio 21 mar 2019, 11:51 Martin Perina <mperina(a)redhat.com> ha scritto:
On Wed, Mar 20, 2019 at 10:38 PM <simtiaz(a)ncsu.edu> wrote:
> I see the github project ovirt-engine (
> https://github.com/oVirt/ovirt-engine) is registered on Coverity Scan
> for routine analysis (
> https://scan.coverity.com/projects/ovirt-engine?tab=project_settings).
>
> My question is -
> 1) do we only build and analyze the master branch on Coverity?
>
Yes
> 1a) If yes, why do we not analyze the other branches?
>
Every patch needs to be merged to master before backport any stable
release branch, so it wouldn't add too much value to perform coverity scan
also on stable branches
next question is: who is looking at coverity reports other than Nasif?
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/V5XEPILH4NZ...
>
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IYUBQ5DBYMX...
8:45 p.m.
New subject: Is only master branch of ovirt-engine analyzed on coverity scan?
On Thu, Mar 21, 2019 at 6:06 PM Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Il gio 21 mar 2019, 11:51 Martin Perina <mperina(a)redhat.com> ha scritto:
>
>
> On Wed, Mar 20, 2019 at 10:38 PM <simtiaz(a)ncsu.edu> wrote:
>
>> I see the github project ovirt-engine (
>> https://github.com/oVirt/ovirt-engine) is registered on Coverity Scan
>> for routine analysis (
>> https://scan.coverity.com/projects/ovirt-engine?tab=project_settings).
>>
>> My question is -
>> 1) do we only build and analyze the master branch on Coverity?
>>
>
> Yes
>
>> 1a) If yes, why do we not analyze the other branches?
>>
>
> Every patch needs to be merged to master before backport any stable
> release branch, so it wouldn't add too much value to perform coverity scan
> also on stable branches
>
next question is: who is looking at coverity reports other than Nasif?
I'm one of receivers of those emails, but I haven't got them for quite a
long time. This week I've received already 2 emails, I've processed the the
1st one and asked relevant developers to fix issues introduced by their
patches. Tomorrow I will process the 2nd one.
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/V5XEPILH4NZ...
>>
>
>
> --
> Martin Perina
> Manager, Software Engineering
> Red Hat Czech s.r.o.
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IYUBQ5DBYMX...
>
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
2071
days inactive
2072
days old
3 comments
3 participants
participants (3)
-
Martin Perina -
Sandro Bonazzola -
simtiaz＠ncsu.edu