Bug #17624
Rethink how we deal with Jenkins failures
Start date:
Due date:
% Done:
0%
Description
As the RM responsible for 4 releases in a row, I’m not comfortable with having to keep an eye on Jenkins failures right afterwards; but given the increased tempo on the Firefox side, it doesn’t leave much room to breathe anyway.
This led me to wonder why Jenkins access/notifications should be limited to RMs; extending that at least to FT would allow for some members to keep an eye on those as well, without having to have one RM triage issues first.
This is a reminder to start a discussion on this topic, likely across -rm & -foundations.
For background, some initial discussion on this topic happened in 2019, in the “Analyzing failure notifications for Jenkins jobs” thread, on the RMs mailing list.
Subtasks
History
#1 Updated by intrigeri 2020-04-16 09:47:10
- Description updated