I think the last conversation we had on it with Allon said it's not bringing enough value and we should consider dropping it.
Especially since it's not integrated with CI well and you need to manually scan the results on a weekly basis.

I vote to drop it, not sure how cost-effective it is and if we want to improve oVirt security, we need to look into better CI integrated solutions that
will run as part of check-patch. 

On Fri, Jun 15, 2018 at 3:31 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi,
I see ovirt-engine_master_coverity-analysis[1] has been disabled, last build (successfull) on March 19 2018.

https://scan.coverity.com/ has an announce asking to change password starting March 16th 2018.
Is the job disabled due to this? Can we re-enable it? Is it considered not useful and should we drop it?


--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   


_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@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/infra@ovirt.org/message/HFMLHGSNH6BGPPDLZRM5WRRNREAXCZKF/




--

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA

TRIED. TESTED. TRUSTED.
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)