Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com
 designates 209.85.215.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E2F3D81.4000609@apache.org>
References: <4E2F34B2.6030000@apache.org>
	<4E2F37A6.1040300@apache.org>
	<CALhtWkdRrSG08i5g0Tg+Md4C0FAMx6x1q0DK13jHECP5Djj8Dw@mail.gmail.com>
	<4E2F3D81.4000609@apache.org>
Date: Tue, 26 Jul 2011 18:21:06 -0400
Message-ID: 
 <CALhtWkcSHw+AwGH--7zkQ=zXXsFmaqw3=9u1whU=gRuiRWsDNw@mail.gmail.com>
Subject: Re: [jenkins] Two distributed builds share the same workspace
From: Benson Margulies <bimargulies@gmail.com>
To: builds@apache.org
Content-Type: text/plain; charset=UTF-8

I did two things:

1) I changed the jobs each to have their own workspace.

2) I changed them to hold the Maven latch, so multiple platforms
cannot run in parallel.

On Tue, Jul 26, 2011 at 6:19 PM, Dennis Lundberg <dennisl@apache.org> wrote:
> Thanks Benson!
>
> Was this a change specifically for Solaris or was it one change that
> affects all the Labels used?
>
> On 2011-07-27 00:16, Benson Margulies wrote:
>> I fixed this by changing the workspace path for the -m2 job. I turned
>> out to have karma.
>>
>> On Tue, Jul 26, 2011 at 5:54 PM, Dennis Lundberg <dennisl@apache.org> wrote:
>>> Hi again
>>>
>>> I see now that we have the same problem on OS X, where both jobs are doing:
>>>
>>> Deleting
>>> /Users/hudson/hudson-slave/maven-site-plugin-3.x/workspace/jdk/JDK 1.5
>>> (latest)/label/osx/target
>>>
>>> One job was almost certainly copied from the other, when it was set up.
>>>
>>>
>>> On 2011-07-26 23:42, Dennis Lundberg wrote:
>>>> Hi
>>>>
>>>> I've investigated some odd build failures on the Solaris slaves for the
>>>> builds of maven-site-plugin. There are two builds of the same source
>>>> code, but with different versions of Maven. Here are the jobs:
>>>>
>>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-site-plugin-3.x/
>>>>
>>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-site-plugin-3.x-m2/
>>>>
>>>> These jobs are set up to build on 4 generic OSes, including the generic
>>>> Solaris label. After analyzing the logs I found that both jobs start by
>>>> doing this:
>>>>
>>>> Deleting
>>>> /zonestorage/hudson/home/hudson/hudson-slave/maven-site-plugin-3.x/workspace/jdk/JDK
>>>> 1.5 (latest)/label/Solaris/target
>>>>
>>>> So when an SVN change triggers a build, or rather two builds in this
>>>> case, the first job is abruptly interrupted by the second one when the
>>>> second one simply deletes the entire workspace of the first.
>>>>
>>>> However the job "maven-site-plugin-3.x-m2" should have it's own
>>>> workspace, called "maven-site-plugin-3.x-m2", on the Solaris slave
>>>> shouldn't it?
>>>>
>>>> Is this something that can be configured or is automagical?
>>>>
>>>
>>>
>>> --
>>> Dennis Lundberg
>>>
>>
>
>
> --
> Dennis Lundberg
>