Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of castagna.lists@googlemail.com
 designates 74.125.82.175 as permitted sender)
Message-ID: <4EAC209A.1040000@googlemail.com>
Date: Sat, 29 Oct 2011 16:49:46 +0100
From: Paolo Castagna <castagna.lists@googlemail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: jena-dev@incubator.apache.org
Subject: Re: Jenkins builds - various
References: <4EAB0B70.1070508@apache.org> <4EAB0FF4.4080305@googlemail.com>
 <4EABBD0D.1080507@apache.org> <4EABD83E.3000800@apache.org>
In-Reply-To: <4EABD83E.3000800@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Andy Seaborne wrote:
> I may have "fixed" the build for "Jena IRI".
> 
> Having created a temporary job that worked, I deleted the Jenkins job 
> completely and created a new one.
> 
> Otherwise it was seeing old files (specifically, a POM with a relative 
> parent; also I had one instance of it reporting a parse error in the 
> parent POM chain ... but I hadn't checked anything in.
> 
> The error occurs elsewhere (e.g. Jena_Core) but I've run out of energy 
> to fix that, then the next one and the next one, ....
> 
> Deleting the workspace of a job does not fix the problem, nor does a 
> clean checkout.
> 
> Slave machine "windows1" looks to be a bad machine to get for a job. But 
> it seems to be the machine you get if you don't restrict the job, 
> possibly it's lightly because it doesn't work very well but I can't 
> gather concrete evidence.
> 
> I'm setting jobs to "ubuntu"
> 
> Sorry about the noise on jena-commits ...

Hi Andy

Just an hypothesis to explain these problems.

The machines used by Jenkins have a Maven repository used to cache artifacts
including pom.xml files. Maybe, for some reason, one or more pom.xml files in
the Maven cache on the machines used by Jenkins have not been updated.

Feel free to ignore Jenkins and just make all the changes you want to make,
I'll then look at what's going on with Jenkins and fix the problems.
Don't waste time with it, if you don't want to.

Having two pom.xml files double the amount of testing, having some projects
using pom.xml (old) and pom2.xml (new) and other use pom.xml (new) and
pom1.xml (old), just increase the probability of making mistakes.

Paolo

> 
>     Andy