On 10 May 2017 at 02:11, Zachary Ware wrote:
> On Tue, May 9, 2017 at 11:04 AM, Chris Angelico wrote:
>> On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith wrote:
>>> Please do not send automated buildbot state transition mail to _this_
>>> list. Leave this low traffic list to communication from
2017-05-09 18:11 GMT+02:00 Zachary Ware :
>> Agreed. Maybe a new list "buildbot-sta...@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 w
On Tue, May 9, 2017 at 11:04 AM, Chris Angelico wrote:
> On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith 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
2017-05-09 18:04 GMT+02:00 Chris Angelico :
> Agreed. Maybe a new list "buildbot-sta...@python.org"?
Ok. I like this name.
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 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 "build
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
wrote:
> Hi,
>
> I would like to get an e
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 build
