Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Matthew Treinish
On Wed, Apr 13, 2016 at 05:12:08PM -0500, Dolph Mathews wrote: > On Wed, Apr 13, 2016 at 2:37 PM, Emilien Macchi wrote: > > > On Wed, Apr 13, 2016 at 12:13 PM, Matthew Treinish > > wrote: > > > On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Ian Wienand
On 04/14/2016 03:22 AM, Jeremy Stanley wrote: Mentioned in IRC as well, but would an RSS/ATOM feed be a good compromise between active notification and focus on the dashboard as an entry point to researching job failures? For myself, simply ordering by date on the log page as per [1] would

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Dolph Mathews
On Wed, Apr 13, 2016 at 2:37 PM, Emilien Macchi wrote: > On Wed, Apr 13, 2016 at 12:13 PM, Matthew Treinish > wrote: > > On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: > >> Hi, > >> > >> Current OpenStack Infra Periodic jobs do not send

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Emilien Macchi
On Wed, Apr 13, 2016 at 12:13 PM, Matthew Treinish wrote: > On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: >> Hi, >> >> Current OpenStack Infra Periodic jobs do not send e-mails (only >> periodic-stable do), so I propose to create periodic-ci-reports >>

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Matthew Treinish
On Wed, Apr 13, 2016 at 05:22:28PM +, Jeremy Stanley wrote: > On 2016-04-13 12:58:47 -0400 (-0400), Matthew Treinish wrote: > > So, sure I understand the attraction of an active notification. > [...] > > Instead, of pretending the ML work for doing this I think it'll be > > better if we

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Jeremy Stanley
On 2016-04-13 12:58:47 -0400 (-0400), Matthew Treinish wrote: > So, sure I understand the attraction of an active notification. [...] > Instead, of pretending the ML work for doing this I think it'll be > better if we concentrate on making the dashboard for this better. Mentioned in IRC as well,

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Matthew Treinish
On Wed, Apr 13, 2016 at 06:22:50PM +0200, Ihar Hrachyshka wrote: > Matthew Treinish wrote: > > > On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: > > > Hi, > > > > > > Current OpenStack Infra Periodic jobs do not send e-mails (only > > > periodic-stable do),

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Ihar Hrachyshka
Matthew Treinish wrote: On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: Hi, Current OpenStack Infra Periodic jobs do not send e-mails (only periodic-stable do), so I propose to create periodic-ci-reports mailing list [1] and to use it when our periodic

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Matthew Treinish
On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: > Hi, > > Current OpenStack Infra Periodic jobs do not send e-mails (only > periodic-stable do), so I propose to create periodic-ci-reports > mailing list [1] and to use it when our periodic jobs fail [2]. > If accepted, people who

[openstack-dev] [all] create periodic-ci-reports mailing-list

2016-04-13 Thread Emilien Macchi
Hi, Current OpenStack Infra Periodic jobs do not send e-mails (only periodic-stable do), so I propose to create periodic-ci-reports mailing list [1] and to use it when our periodic jobs fail [2]. If accepted, people who care about periodic jobs would like to subscribe to this new ML so they can