Bug 1591276

Summary:	Automated way to run coverity runs on project every week.
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	amukherj, bugs, gluster-infra, jeff, nigelb, srangana
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Process-Automation
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-20 03:23:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amar Tumballi 2018-06-14 13:01:05 UTC

# Description of problem:

Today, we do have a coverity run which happens on the master branch with internal Red Hat coverity license, but we can't get a dashboard for the coverity, which is very critical for us to measure which new issues are getting introduced, what is the rate of fixing of bugs, and what are the severity of the issues etc.

Hence, we are requesting a way to run our project in scan.coverity.com (Ref: https://scan.coverity.com/projects/gluster-glusterfs?tab=overview )

The issue here is, we need to keep uploading our code here ourselves (well, we can automate this process, and hence the bug). 

# Additional info:

Build with every possible flag, so it covers maximum code.
Frequency of scan be once in a week.

Let us know what more is needed.

Comment 1 Nigel Babu 2018-08-20 03:05:01 UTC

This now exists and we run it daily, actually.

Comment 2 Amar Tumballi 2018-08-20 03:23:57 UTC

yes, I see the results. Wonderful! Thanks.