Bug 1377533

Summary:	Run check-bugs.py on weekly basis in Jenkins and have it send emails
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
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, mscherer, nigelb
Target Milestone:	---	Keywords:	Triaged
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-04-12 14:50:39 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:

Description Niels de Vos 2016-09-20 03:45:21 UTC

Description of problem:
check-bugs.py is a script that generates a list of bugs and patches that are in an incorrect state. In the default execution mode, it will go through all open changes and matches the status of bugs with them.

The script generates a plain-text output, like http://www.gluster.org/pipermail/gluster-devel/2016-September/050941.html

At the moment this script is running as a cronjob on bugs.cloud.gluster.org and I forward the email manually after a minimal check. Instead of running it from cron, it can run in Jenkins and send the output to gluster-devel directly.

The script is part of https://github.com/gluster/release-tools, as it can be used for verifying the bug status of trackers/versions/buglists and so on.

Comment 1 M. Scherer 2016-09-21 08:01:37 UTC

I would rather try to not run it from jenkins, because in a ideal world,i would like the builders be unable to send email. Any reason to not keep the cronjob approach ?

Comment 2 Niels de Vos 2016-09-21 13:19:40 UTC

A cron job is fine too, but it should get sent from an email address (not mine) and accepted by the mailinglist without the need for approval.

We have other jobs running in Jenkins that need to send emails (like the release announcement to packagers). If those jobs can do it, this one should be able to do it too?

Comment 3 Nigel Babu 2016-09-26 05:51:05 UTC

I'm going to rework the release job so it's likely it will not do an announce in the future. I'm figuring out the scope of the rework and it requires multiple conversations. For now it will send emails, but I hope to eliminate that eventually.

Comment 4 Niels de Vos 2016-09-26 09:22:46 UTC

The output  of the script needs some manual review. The script is not perfect, and sometimes bugs can be in 'incorrect' status on purpose. Complete automated correction of 'incorrect' bug status will be difficult.

Comment 5 Amar Tumballi 2018-04-12 14:50:39 UTC

I feel, the bugs from now on will get transitioned automatically to MODIFIED/POST based on the status provided by the authors. Ref: https://review.gluster.org/19565

Feel free to open this if above doesn't satisfy the need. (CURRENTRELEASE as this is now deployed)