Email notifications on buildbot failures
Hi,
I would like to get an email notification each time the state of a buildbot changed from green (success) to red (failed).
Maybe we can start with the master branch, but my long term plan is to watch all branches (especially 2.7, 3.5, 3.6 and master), but maybe exclude the special custom buildbots.
Can I use this list, or do you prefer that I create a different list? If you prefer a different list, which name do you suggest?
I'm already watching "daily" (almost) buildbot waterfalls, but the UI is not efficient, I have to scroll, ignore known broken buildbots, ignore offline builders, etc. My request is to only get a notification for the green => red state change, not any state change for now, that would avoid spaming the list.
I always would like to use a mailing list to coordonate efforts to fix buildbot issues.
Victor
Please do not send automated buildbot state transition mail to _this_ list. Leave this low traffic list to communication from humans about buildbots and infrastructure (the purpose as I understand it).
-gps
On Tue, May 9, 2017 at 8:01 AM Victor Stinner <victor.stinner@gmail.com> wrote:
Hi,
I would like to get an email notification each time the state of a buildbot changed from green (success) to red (failed).
Maybe we can start with the master branch, but my long term plan is to watch all branches (especially 2.7, 3.5, 3.6 and master), but maybe exclude the special custom buildbots.
Can I use this list, or do you prefer that I create a different list? If you prefer a different list, which name do you suggest?
I'm already watching "daily" (almost) buildbot waterfalls, but the UI is not efficient, I have to scroll, ignore known broken buildbots, ignore offline builders, etc. My request is to only get a notification for the green => red state change, not any state change for now, that would avoid spaming the list.
I always would like to use a mailing list to coordonate efforts to fix buildbot issues.
Victor
Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith <greg@krypto.org> wrote:
Please do not send automated buildbot state transition mail to _this_ list. Leave this low traffic list to communication from humans about buildbots and infrastructure (the purpose as I understand it).
Agreed. Maybe a new list "buildbot-status@python.org"?
ChrisA
On Tue, May 9, 2017 at 11:04 AM, Chris Angelico <rosuav@gmail.com> wrote:
On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith <greg@krypto.org> wrote:
Please do not send automated buildbot state transition mail to _this_ list. Leave this low traffic list to communication from humans about buildbots and infrastructure (the purpose as I understand it).
That is indeed the intended purpose :)
Agreed. Maybe a new list "buildbot-status@python.org"?
I'd agree with this, or with using python-checkins@. Dusty, commented code in the master config looks like notifications used to go there, but it was before my time and I don't know why it was stopped (if indeed it ever happened).
-- Zach
2017-05-09 18:11 GMT+02:00 Zachary Ware <zachary.ware+pydev@gmail.com>:
Agreed. Maybe a new list "buildbot-status@python.org"?
I'd agree with this, or with using python-checkins@. Dusty, commented code in the master config looks like notifications used to go there, but it was before my time and I don't know why it was stopped (if indeed it ever happened).
I'm not interested by python-checkins@, so at least me would like to get two separated lists :-) It's not too difficult to subscribe to two different lists ;-)
Victor
On 10 May 2017 at 02:11, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
On Tue, May 9, 2017 at 11:04 AM, Chris Angelico <rosuav@gmail.com> wrote:
On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith <greg@krypto.org> wrote:
Please do not send automated buildbot state transition mail to _this_ list. Leave this low traffic list to communication from humans about buildbots and infrastructure (the purpose as I understand it).
That is indeed the intended purpose :)
Agreed. Maybe a new list "buildbot-status@python.org"?
I'd agree with this, or with using python-checkins@. Dusty, commented code in the master config looks like notifications used to go there, but it was before my time and I don't know why it was stopped (if indeed it ever happened).
My vague recollection is that it was originally turned on, but then switched off for generating too many false alarms (i.e. problems with the buildbots rather than problems with the test results). Separating out a "stable" subset of buildbots that were expected to stay green came later.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (5)
-
Chris Angelico -
Gregory P. Smith -
Nick Coghlan -
Victor Stinner -
Zachary Ware