On Fri, May 6, 2016 at 7:55 AM Matej Novotny <[email protected]> wrote:
> Hey there > > Sorry to spam you guys, totally didn't mean to flood you with email like > that[1]. > Not your fault, you fixed the build not broke it. > > You had all the weld 1.x jobs turned off so I suppose this is the main > source of problems. > Besides one job sending 50 emails... not a great idea imo. > > > But what I wanted to point out is that you need to review the settings of > those jobs. > My commits introduced new profiles for Weld (Weld1, Weld2, Weld3). The old > '-PWeld' will not trigger a correct build (not sure what will happen). > And the first failed job I saw had this misconfigured -> > https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20Weld%201.1.33/12/consoleFull > It was running with ' > https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20Weld%201.1.33/12/consoleFull > ' > > So reviewing and correcting the job settings will probably keep the spam > at bay :) > IMHO we can do a lot to clean up these jobs. Do we need all of them in your opinion? Key weld versions to test with? > > Regards > Matej > > [1] https://dropmyemail.files.wordpress.com/2012/07/9-email.jpg > > ----- Original Message ----- > > From: "John D. Ament" <[email protected]> > > To: "deltaspike" <[email protected]> > > Sent: Friday, May 6, 2016 1:30:13 PM > > Subject: Cutting down on jenkins email > > > > All, > > > > If you're subscribed to commits@ you'll have seen that there was an > influx > > of about 700 emails last night. While its good that Matej's changes > fixed > > a lot of broken builds, that's a lot of emails to get through. Right now > > our jenkins jobs send email for each failing module. IMHO it should just > > be at a job level (since we have a lot of modules). > > > > Anyone opposed to only sending an email per job instead of per module? > > > > John > > >
