Bug 1597351

Summary:	Smoke should fail on commits against closed github issues
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, 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-11-12 09:21:35 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 Shyamsundar 2018-07-02 17:30:05 UTC

We should start failing smoke on commits that use closed github issues.

Once closed, an issue is assumed to be done, and hence future commits are really bug fixes or further enhancements and should be called out as such, than using the same issue to pound in more commits.

@amarts thoughts?

Comment 1 Amar Tumballi 2018-07-02 18:07:47 UTC

> @amarts thoughts?

Agree! lets do it.

Comment 2 Nigel Babu 2018-10-05 06:56:23 UTC

Sounds good. Adding to Sprint 5!

Comment 3 Nigel Babu 2018-11-12 09:21:35 UTC

Fixed in https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/177