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.
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 ?
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?
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.
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.
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)