Bug 1631390

Summary:	Run smoke and regression on a patch only after passing clang-format job
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	bugs, gluster-infra, srangana, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 12:53:53 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-09-20 13:24:26 UTC

Description of problem:
Now, 'clang-format' job runs as part of smoke! As it is a mandatory, and as it is a new change, there is high chance of smoke getting negative vote for this job compared to others. It makes sense to run it first, and then only run other jobs. Otherwise, we will be spending too many resources even when we 'technically know' the vote is -1.

Version-Release number of selected component (if applicable):
master

How reproducible:
100%

Steps to Reproduce:
1. Send a patch with known format change issues
2. Trigger regression with marking Verified as +1.
3. See that all smoke job, and regression job still starts and completes


Expected results:
only if clang-format passes, others should be allowed.

Comment 1 Nigel Babu 2018-10-03 08:47:43 UTC

This going to take some time to tweak and get right. I'm going to tackle this in sprint 5.

Comment 3 Worker Ant 2020-03-12 12:53:53 UTC

This bug is moved to https://github.com/gluster/project-infrastructure/issues/34, and will be tracked there from now on. Visit GitHub issues URL for further details