Bug 1625489

Summary:	No need to run 'fedora-smoke' job on release branches (3.12/4.1)
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.12	CC:	bugs, gluster-infra, nigelb
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:	2018-09-05 10:44:15 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-05 03:57:29 UTC

Description of problem:
'fedora-smoke' job is to make sure we don't have any warnings on gcc8 (fedora28) when compiled. The fixes for it just landed in upstream master... and are not planned to be backported to release branches (for both 3.12/4.1), hence they are expected to fail. It makes sense to not to have this job run for release branches.

Version-Release number of selected component (if applicable):
3.12 / 4.1

How reproducible:
100%

Steps to Reproduce:
1. submit a patch to release branch.

Actual results:
fedora-smoke test fails.

Expected results:
No test at all (as it always fails)

Additional info:
Once release_5.0 branch is made, this job can run there, to preserve sanity, but not now.

Comment 1 Nigel Babu 2018-09-05 10:44:15 UTC

Fixed in https://review.gluster.org/c/build-jobs/+/21088