Page MenuHomePhabricator
Create Task
Maniphest T89375

Move browser test alerts to responsible teams' channels from -releng
Closed, ResolvedPublic
Actions

Description

In the overall effort to increase the distributed ownership of testing at WMF (and especially of browser test ownership) I would like us to move the browser test failure/fixed notifications to the relevant teams' channels and remove them from the -releng channel.

The last part of the sentence is potentially contentious, but I want to keep it. I want the onus to be on the teams writing the code, not a central "we'll maintain your tests for you" person/team. A pretty efficient way of doing that is to make them see the announcements and not have us (RelEng) respond to them immediately.

The next/related step is to make browser tests voting...

Related Objects
Search...

Event Timeline

greg created this task.Feb 12 2015, 7:45 PM
greg raised the priority of this task from to Medium.
greg updated the task description. (Show Details)
greg added a project: Release-Engineering-Team.
greg subscribed.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 12 2015, 7:45 PM
greg added a project: Browser-Tests-Infrastructure.Feb 24 2015, 4:14 PM
greg set Security to None.
greg assigned this task to • Cmcmahon.Feb 25 2015, 4:27 PM
greg added a subscriber: Ryasmeen.
• Cmcmahon added a subscriber: zeljkofilipin.Feb 26 2015, 4:42 PM
zeljkofilipin added a subtask: T66103: send Echo and Flow (and any Collaboration team extensions with browser tests) browser test job notices to #wikimedia-collaboration channel.Feb 26 2015, 4:46 PM
• dduvall mentioned this in T88706: [Quarterly Success Metric] By team test history.Mar 5 2015, 12:15 AM
zeljkofilipin added a comment.Mar 25 2015, 1:40 PM

Is this done?

greg added a comment.Mar 25 2015, 9:13 PM
In T89375#1148602, @zeljkofilipin wrote:

Is this done?

I haven't seen any gerrit patches fly by nor audited the config.

zeljkofilipin added a project: Continuous-Integration-Infrastructure.Mar 26 2015, 9:25 AM
greg removed • Cmcmahon as the assignee of this task.Mar 31 2015, 3:48 PM
greg raised the priority of this task from Medium to High.
greg added a subscriber: Jdlrobson.

Setting to higher-than-normal (which means "high") due to conversation and email thread on the mobile list with @Jdlrobson

gerritbot subscribed.Apr 2 2015, 7:33 AM

Change 201083 had a related patch set uploaded (by Zfilipin):
Notify Collaboration team of failing browser tests

https://gerrit.wikimedia.org/r/201083

gerritbot added a project: Patch-For-Review.Apr 2 2015, 7:33 AM
hashar renamed this task from Move browser test alerts to responsible teams' channels from -releng to Move browser test alerts to responsible teams' channels from -releng (tracking).EditedApr 2 2015, 9:03 AM
hashar edited projects, added Tracking-Neverending; removed Patch-For-Review.
hashar subscribed.

Please disregard patch https://gerrit.wikimedia.org/r/201083 which changes the email notification for the collaboration team.

I have made this task a tracking bug. Please fill sub tasks as appropriate.

Krinkle moved this task from Untriaged to Backlog on the Continuous-Integration-Infrastructure board.Apr 13 2015, 4:56 PM
hashar edited projects, added Continuous-Integration-Config; removed Continuous-Integration-Infrastructure.Jun 9 2015, 3:52 PM
• dduvall moved this task from INBOX to Backlog (ARCHIVED) on the Release-Engineering-Team board.Jun 9 2015, 3:53 PM
zeljkofilipin removed a project: Browser-Tests-Infrastructure.Jun 9 2015, 3:54 PM
hashar removed a project: Continuous-Integration-Config.Jun 9 2015, 3:54 PM

We have agreed this has no implementation opportunity for now. We need to figure out which browser tests belong to which team then work with each team to find which notification channels they want.

hashar added a comment.Jun 9 2015, 7:30 PM

From the Browser-Tests weekly checkin: we need to list all browser tests jobs, find the team responsible for each and ask them their favorite notification channels / lists.

greg added a project: Browser-Tests-Infrastructure.Sep 9 2015, 11:20 PM
greg lowered the priority of this task from High to Medium.Sep 24 2015, 1:26 AM
zeljkofilipin renamed this task from Move browser test alerts to responsible teams' channels from -releng (tracking) to Move browser test alerts to responsible teams' channels from -releng.Sep 30 2015, 3:30 PM
zeljkofilipin edited projects, added Continuous-Integration-Infrastructure; removed Browser-Tests-Infrastructure.
greg added a comment.Sep 30 2015, 3:45 PM

@zeljkofilipin: why remove browser-tests project?

zeljkofilipin added a project: Browser-Tests-Infrastructure.Sep 30 2015, 4:03 PM

@greg: I am trying to make sense of the huge Browser-Tests board. :/ Let's see if grouping tasks helps.

zeljkofilipin moved this task from Inbox to CI on the Browser-Tests-Infrastructure board.Sep 30 2015, 4:04 PM
hashar removed projects: Continuous-Integration-Infrastructure, Release-Engineering-Team.Oct 28 2015, 1:48 PM
greg closed this task as Resolved.Jun 21 2016, 7:28 AM
greg claimed this task.

The purpose of this task is mostly superseded by T134492, though I'd still like to reduce our spam in -releng. Resolving for now.

Restricted Application added a project: User-greg. · View Herald TranscriptJun 21 2016, 7:28 AM
Danny_B moved this task from Tag to Should be Goal instead on the Tracking-Neverending board.Jul 11 2016, 7:11 PM
• Phabricator_maintenance added a project: Goal.Aug 13 2016, 8:41 PM
• Phabricator_maintenance removed a project: Tracking-Neverending.Aug 13 2016, 9:01 PM
greg closed subtask T66103: send Echo and Flow (and any Collaboration team extensions with browser tests) browser test job notices to #wikimedia-collaboration channel as Declined.May 20 2017, 4:31 PM
Restricted Application added projects: User-Ryasmeen, Release-Engineering-Team (Kanban). · View Herald TranscriptMay 20 2017, 4:31 PM
• Phabricator_maintenance edited projects, added RelEng-Archive-FY201718-Q1; removed Release-Engineering-Team (Kanban).Sep 26 2017, 11:48 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL