I'll take a look at this. Gav...
> -----Original Message----- > From: lewis john mcgibbney [mailto:lewis.mcgibb...@gmail.com] > Sent: Thursday, 11 August 2011 7:42 PM > To: builds@apache.org > Subject: Nutch Trunk build failure for over 1 year > > Hi builds team, > > As a new committer on the Apache Nutch project, I'm on the war path to get > our trunk build working as it was embarrassingly last seen working just over > 1 year 1 month ago on 7-Jul-2010. > > If I point to the last log output showing the build failing I was wondering if > anyone would be kind enough to point me in the right direction as to > whether the build is failing due to problems on the dev@nutch side of things > or whether it is the way that the Jenkins job in configured. From viewing the > build specifics and log output shown here [1], I can't help but think that it is > the latter of the two due to the following output: > > + /export/home/hudson/tools/ant/latest/bin/ant > -Dversion=2011-08-11_04-01-22 -Dtest.junit.output.format=xml nightly > /tmp/hudson2424857644284663135.sh: line 7: > /export/home/hudson/tools/ant/latest/bin/ant: No such file or directory > > > I must admit I am completely new to the Hudson build environment, having > only undertaken reading of the wiki and some other resources, therefore I > have not requested a Jenkins account from my PMC Chair. > > Any information would be greatly appreciated as we are pretty keen to get > this build working and to do so within a reasonable timeframe. Any info I > could obtain behind the build failing due to errors on the code side would > also enable me to report directly back to devs@nutch in an attempt to > rectify. > > Thank you very much > > [1] https://builds.apache.org/view/M-R/view/Nutch/ > > -- > *Lewis*
