> -----Original Message----- > From: Jeff Eastman [mailto:j...@windwardsolutions.com] > Sent: Wednesday, 28 December 2011 3:31 PM > To: dev@mahout.apache.org; infrastruct...@apache.org > Subject: Re: Build failed in Jenkins: mahout-nightly #737 > > +infra@
All build related questions should go to the bui...@apache.org list. > > Well, yes, I guess everybody is ignoring them. But that kinda begs the > question of why we even bother to have Jenkins if we are going to always > ignore its warnings? I'm a big fan of continuous integration and I've managed > its administration before so I understand the challenges. But this seems > kinda goofy to me. It is not up to infra to check projects failed builds! It is up to the project. It is also up to the project to configure their Jenkins configs. Now, if the project needs any pre-reqs installed on any slaves to help make the build pass, by all means ask the builds@ list, otherwise what are we infra expected to do? If Jenkins isn’t working out for you, maybe try Buildbot or Continuum , see ci.apache.org for more. Gav... > > > On 12/27/11 9:53 PM, Sean Owen wrote: > > It's all errors in the Apache infrastructure, rather than a real test > > failure. At least, stuff passes for me locally, and that's what's > > important. > > So I'm ignoring these. > > > > On Tue, Dec 27, 2011 at 9:34 PM, Jeff Eastman > > <jeast...@windwardsolutions.com> wrote: > >> I'm getting a lot of these emails yet all the tests run locally for > >> me. Does anybody have an idea what the problem is? This close to a > >> release it would be really nice to have Jenkins on our side. > >> Jeff > >> > >
