> -----Original Message----- > From: David Nalley [mailto:[email protected]] > Sent: Wednesday, September 12, 2012 1:17 PM > To: [email protected] > Subject: test lifecycle > > Hi folks, > > I am thinking about making some changes to jenkins and figured I'd > toss it up here before I do it to make sure no one disagrees. > > Here's my frustration: We are getting spammed by lots of jenkins > notices, many needlessly. > > Prime example: junit failures when the build also failed. IMO we > shouldn't even try running the unit tests as there is an explicit > dependency to compile and we 'know' it won't build. > > So I'd run build-$branch on each commit - if successful it would > trigger build-marvin, build-docs, build-apidocs, and junit. If junit > succeeds build packages (though eventually we probably want to > run-marvin first, but for the moment) +1 BTW, is there a way to unsubscribe notification from jenkins? So many emails are send to my mail box, every day... But hopefully, the build will be fixed today.
> > Thoughts, comments, flames? > > --David
