Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGaRif27FTP--brKLYuSa2oTyEsobAqcAumKoir9h8rhNDkKbA@mail.gmail.com>
References: 
 <CAGaRif2iNP-S0h0cw+5ro+qtu8fyPE2t9ux=snkuOp0CR3t2CA@mail.gmail.com>
 <CAOJNCYe6UxB=kV8JAZN0ekaxMkan8rPdm9fPMC9d2dSNn5ZqAQ@mail.gmail.com>
 <CAGaRif27FTP--brKLYuSa2oTyEsobAqcAumKoir9h8rhNDkKbA@mail.gmail.com>
From: Olivier Lamy <olamy@apache.org>
Date: Thu, 11 Aug 2011 12:18:53 +0200
Message-ID: 
 <CAPoyBqTyNPS9MOdcgHBxFu0TYeeDvpw_rc_fhsJDtMDEEY=BxA@mail.gmail.com>
Subject: Re: Nutch Trunk build failure for over 1 year
To: builds@apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hello,
I have just created an other job with use of ant step rather than the
script one with hardcoded path to ant.
But IMHO there is some ivy setup to add in the project.
See https://builds.apache.org/job/Nutch-trunk-ant/3/console

2011/8/11 lewis john mcgibbney <lewis.mcgibbney@gmail.com>:
> Thank you both for getting back.
>
> In response to your comments Niklas, can you comment on where it would be
> preferred that we bind the builds to, e.g. Ubuntu or Solaris slaves? It
> terms of preferrance from the dev@nutch team, I'm not sure we have a
> preferrence at the moment, and would just like to project to build, however
> if you could shine some light on pro's con's of both configurations I would
> be grateful.
>
> Yes I had no seen these errors due to unresolved dependencies and we can fix
> this with little effort, I think that these haven't been seen to due to the
> fact that we hadn't seen a successful build in a looong time and no one was
> looking into it.
>
> With regards to get a stable build back on track, are these the only
> problems you envisage e.g. correcting both of the above? If this is the case
> then I would like to think that this might be easier than I first thought,
> however I am no holding my breath.
>
> Thanks again
>
> On Thu, Aug 11, 2011 at 11:06 AM, Niklas Gustavsson <niklas@protocol7.com>wrote:
>
>> On Thu, Aug 11, 2011 at 11:41 AM, lewis john mcgibbney
>> <lewis.mcgibbney@gmail.com> wrote:
>> > 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
>>
>> There are some different types of problems with the build. First of
>> all, it's not bound to any particular set of slaves which means it
>> will sometimes build on ubuntu slaves. These have ant installed under
>> /home/hudson/tools/ant/latest/bin/ant. The /export directory is only
>> available on the solaria's slaves. So fix this or perhaps bind your
>> build to either ubuntu or solaris slaves.
>>
>> Also, when the build happens to run on one of the solaris slaves, you
>> run into other issues:
>> https://builds.apache.org/view/M-R/view/Nutch/job/Nutch-trunk/1571/console
>>
>> These you probably understand better than me.
>>
>> /niklas
>>
>
>
>
> --
> *Lewis*
>


-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy