Hi James, Just re-thinking an element of this bitrot job notifications thing ... The openstack-stable-maint list is being spammed with notifications of Diablo/Essex failures: http://lists.openstack.org/pipermail/openstack-stable-maint/2012-November/da... https://jenkins.openstack.org/view/Bitrot/ But the stable-maint team is only responsible for the stable/folsom branch. There are separate essex-maint and diablo-maint teams. The Diablo/Essex failures should be addressed, but I'd prefer to not have those notifications hit the stable-maint list - I fear we're just training the team to ignore the notifications and we'll miss any Folsom failures when they crop up. Thanks, Mark.
Mark McLoughlin <markmc@redhat.com> writes:
Hi James,
Just re-thinking an element of this bitrot job notifications thing ...
The openstack-stable-maint list is being spammed with notifications of Diablo/Essex failures:
http://lists.openstack.org/pipermail/openstack-stable-maint/2012-November/da... https://jenkins.openstack.org/view/Bitrot/
But the stable-maint team is only responsible for the stable/folsom branch. There are separate essex-maint and diablo-maint teams.
The Diablo/Essex failures should be addressed, but I'd prefer to not have those notifications hit the stable-maint list - I fear we're just training the team to ignore the notifications and we'll miss any Folsom failures when they crop up.
I agree -- if you (o-s-m) aren't going to fix it, then you're the wrong people to get the notifications. :) Possible solutions: 1) Add a new list for each branch maint team and have jenkins target the separate lists. 2) Use mailman topics, and have jenkins send out messages with appropriate subjects. 3) Disable email notifications for all but the latest stable branch. If needed, can you reply and add to the CC list the folks who are maintaining the diablo and essex branches? -Jim
On 12 November 2012 14:48, James E. Blair <corvus@inaugust.com> wrote:
Mark McLoughlin <markmc@redhat.com> writes: <SNIP>
I agree -- if you (o-s-m) aren't going to fix it, then you're the wrong people to get the notifications. :) Possible solutions:
1) Add a new list for each branch maint team and have jenkins target the separate lists. 2) Use mailman topics, and have jenkins send out messages with appropriate subjects. 3) Disable email notifications for all but the latest stable branch.
If needed, can you reply and add to the CC list the folks who are maintaining the diablo and essex branches?
Hey, Thanks for following this up, and introducing the bitrot tests.. Seems it identified a fair amount of tasks! Lets go for option 1 please. These are the teams that look after them.. I have just created LP mailing lists, that should be available shortly. https://launchpad.net/~openstack-diablo-maint https://launchpad.net/~openstack-essex-maint Thanks. -- Kind Regards, Dave Walker <Dave.Walker@canonical.com> Engineering Manager, Ubuntu Server
Daviey Walker <dave.walker@canonical.com> writes:
On 12 November 2012 14:48, James E. Blair <corvus@inaugust.com> wrote:
Mark McLoughlin <markmc@redhat.com> writes: <SNIP>
I agree -- if you (o-s-m) aren't going to fix it, then you're the wrong people to get the notifications. :) Possible solutions:
1) Add a new list for each branch maint team and have jenkins target the separate lists. 2) Use mailman topics, and have jenkins send out messages with appropriate subjects. 3) Disable email notifications for all but the latest stable branch.
If needed, can you reply and add to the CC list the folks who are maintaining the diablo and essex branches?
Hey,
Thanks for following this up, and introducing the bitrot tests.. Seems it identified a fair amount of tasks!
Lets go for option 1 please.
These are the teams that look after them.. I have just created LP mailing lists, that should be available shortly. https://launchpad.net/~openstack-diablo-maint https://launchpad.net/~openstack-essex-maint
That change is here: https://review.openstack.org/16086 I'm not sure that emails from jenkins will make it to the LP lists (and you might have to add openstack-hudson as a team member?), so let's be on the lookout for delivery errors after that merges. -Jim
participants (3)
-
corvus＠inaugust.com
-
Daviey Walker
-
Mark McLoughlin