Last modified: 2014-05-21 12:49:04 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66610, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64610 - Create a qa notification list
Create a qa notification list
Status: VERIFIED FIXED
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Tomasz W. Kozlowski
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-29 15:41 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-05-21 12:49 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2014-04-29 15:41:10 UTC
We would like to get notifications of Jenkins success/failures send to a mailing list. Spamming qa is probably not a good idea, so we should have a qa-notification list.
Comment 1 Andre Klapper 2014-05-01 15:37:59 UTC
If QA +1's this request, please change component to "Mailing lists"
Comment 2 Chris McMahon 2014-05-20 20:33:40 UTC
+1, changed component
Comment 3 Tomasz W. Kozlowski 2014-05-20 21:25:15 UTC
Thanks, Chris and Antoine! Before I create this list, I require the following information from you:

1. Who is supposed to be list administrator (please provide at least two addresses)?
2. Are the list archives supposed to be public or private?
3. Should subscription to the list require admin approval or subscriber confirmation only?

These are just the basic settings; you will of course be able to set the details by yourselves once I create the list & forward admin password to you.
Comment 4 Antoine "hashar" Musso (WMF) 2014-05-21 09:35:53 UTC
Hello Tomasz,

Sorry we forgot the basic details, here they are:

> 1. Who is supposed to be list administrator (please provide at least two addresses)?

Both I and Chris:  hashar+wmf@free.fr and cmcmahon@wikimedia.org

> 2. Are the list archives supposed to be public or private?

Public archives.

> 3. Should subscription to the list require admin approval or subscriber confirmation only?

Any user should be able to subscribe. So that would be an open list :-)


We already have two lists suffixed with '-Alerts':

 EventLogging-Alerts
 Multimedia-Alerts

So I guess we can follow that scheme and use QA-Alerts.


Thank you!
Comment 5 Tomasz W. Kozlowski 2014-05-21 11:25:57 UTC
The list has now been created, and I configured it to have public archives, with everyone being able to subscribe to it.

You can configure the rest of the settings, including list description and a terse identifying phrase at the following web page:

    https://lists.wikimedia.org/mailman/admin/qa-alerts

The web page for users of your mailing list is:

    https://lists.wikimedia.org/mailman/listinfo/qa-alerts

I just sent the admin password to the two given e-mail addresses, and made them list administrators.

Please make sure to list the new mailing list at

    https://meta.wikimedia.org/wiki/Mailing_lists/Overview

This request is now closed; enjoy your new mailing list!
Comment 6 Tomasz W. Kozlowski 2014-05-21 11:52:47 UTC
I forgot to mention that the list is subscribed to Gmane under gmane.org.wikimedia.qa.alerts if you are going to link to the archive on the Overview page on Meta.
Comment 7 Antoine "hashar" Musso (WMF) 2014-05-21 12:25:19 UTC
Thank you very much for the gmane registration!
Comment 8 Antoine "hashar" Musso (WMF) 2014-05-21 12:49:04 UTC
I have updated Jenkins to emit emails from jenkins-bot@wikimedia.org and subscribed that address to the list (mail delivery to that address is disabled though).

A first tested worked http://lists.wikimedia.org/pipermail/qa-alerts/2014-May/000000.html



Thank you.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links