Re: Apache Jenkins emails

2016-10-16 Thread Amila Jayasekara
I agree with Suresh. The build system should set up correctly only to notify correct build errors and whenever there is a build failure person who is responsible for the failure should commit to fixing it. On Sun, Oct 16, 2016 at 6:38 PM, Suresh Marru wrote: > since there is popular demand, I ch

Re: Apache Jenkins emails

2016-10-16 Thread Suresh Marru
since there is popular demand, I changed Jenkins to send emails to issues instead. But we still need to ensure Jenkins only complains when there are real build failures and we need to take them seriously. Suresh > On Oct 15, 2016, at 4:44 PM, Douglas Chau wrote: > > +1 > > > On Oct 15, 201

Re: Apache Jenkins emails

2016-10-15 Thread Douglas Chau
+1 On Oct 15, 2016 1:42 PM, "Pankaj Saha" wrote: > +1 > > On Sat, Oct 15, 2016 at 3:44 PM, Sandra Gesing > wrote: > >> +1 >> >> >> >> Sandra Gesing >> Research Assistant Professor, Depa

Re: Apache Jenkins emails

2016-10-15 Thread Pankaj Saha
+1 On Sat, Oct 15, 2016 at 3:44 PM, Sandra Gesing wrote: > +1 > > > > Sandra Gesing > Research Assistant Professor, Department of Computer Science and > Engineering > Computational Scien

Re: Apache Jenkins emails

2016-10-15 Thread Sandra Gesing
+1 Sandra Gesing Research Assistant Professor, Department of Computer Science and Engineering Computational Scientist, Center for Research Computing University of Notre Dame http://www3.nd.

Re: Apache Jenkins emails

2016-10-15 Thread Shameera Rathnayaka
+1 On Sat, Oct 15, 2016 at 3:39 PM Pierce, Marlon wrote: > How about directing the Jenkins messages to the “issues” or another list > besides dev@airavata? > > > > Marlon > > > -- Shameera Rathnayaka