[Engineering] Ownership of Selenium tests

[Željko Filipin]

TLDR: If you care about Selenium tests that run daily[1], please take
ownership of repository (or repositories) that you care about.

Our Selenium tests provide useful feedback, finding problems in several
places, when there is something wrong with:

#1 the repository they are testing (broken production or test code),
#2 beta and/or production clusters,
#3 continuous integration.

It is really important that all tests that run daily are green all the
time. I have started cleaning up tests[2-3].

If there is a failure, we have to investigate and fix it as soon as
possible, ideally in one business day. To be able to do that, we need
contact information for each repository. I have started collecting contact
details [3] from various sources.

What does taking ownership mean? Your e-mail address will be added to
Jenkins job repository configuration[4] and you will receive one e-mail a
day per repository and job, but only if there are any failed jobs. In
short, if you are an owner of one repository with one job, you will receive
0-2 e-mails a day, depending on the stability of the job. It will be your
responsibility to fix the job. If you need help, I will be glad to help.

The contact e-mail address can be one or more people, or a team mailing
list. All I need is a reply if I send an e-mail message to that address,
without having to be a member of a lot of mailing lists.

Jobs for repositories without contact person will be running while they are
passing, and will be deleted when they start failing.

To become a contact person, submit a patch[4] or let me know off-list.

Questions? Comments? Please do let me know.

Željko
--
1: https://integration.wikimedia.org/ci/view/Selenium/
2: https://phabricator.wikimedia.org/T94150
3: https://phabricator.wikimedia.org/T128190
4:
https://phabricator.wikimedia.org/diffusion/CICF/browse/master/jjb/selenium.yaml$1-18
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/engineering/attachments/20160504/1e6020e5/attachment.html>