Build stuck?

2011-07-26 Thread Benson Margulies
I tried to cancel https://builds.apache.org/view/M-R/view/Maven/job/maven-site-plugin-3.x, and now it seems to be in limbo. Can someone with more karma apply a larger hammer?

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Benson Margulies
Some else already clicked on 'Run each configuration sequentially'. So it's already doing one platform at a time. grabbing the lock is thus not going to make it slower. On Tue, Jul 26, 2011 at 6:32 PM, Dennis Lundberg wrote: > On 2011-07-27 00:21, Benson Margulies wrote: >> I did two things: >> >

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Benson Margulies
If you don't want to do this, you have to arrange for a different workspace path on each platform. I don't know how to do that, since this 'label' business is new to me. There is only one workspace path per job, but multiple labels. I'll look into it. On Tue, Jul 26, 2011 at 6:32 PM, Dennis Lund

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Dennis Lundberg
On 2011-07-27 00:21, Benson Margulies wrote: > I did two things: > > 1) I changed the jobs each to have their own workspace. Great, thanks. > 2) I changed them to hold the Maven latch, so multiple platforms > cannot run in parallel. Was this needed? Will that mean that the build will take appro

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Benson Margulies
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 wrote: > Thanks Benson! > > Was this a change specifically for Solaris or was it on

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Dennis Lundberg
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 L

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Benson Margulies
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 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

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Dennis Lundberg
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 Lun

Re: [jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Benson Margulies
I think it's the other way around. Someone used a custom workspace option to force them into the SAME workspace, when the default is the other way around. I could get some karma and fix this, I guess. On Tue, Jul 26, 2011 at 5:42 PM, Dennis Lundberg wrote: > Hi > > I've investigated some odd buil

[jenkins] Two distributed builds share the same workspace

2011-07-26 Thread Dennis Lundberg
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.a

Re: Portals build error

2011-07-26 Thread Woonsan Ko
Thanks a lot! It is back to normal now. Cheers, Woonsan - Original Message > From: Niklas Gustavsson > To: builds@apache.org > Sent: Mon, July 25, 2011 4:10:44 PM > Subject: Re: Portals build error > > On Mon, Jul 25, 2011 at 6:47 PM, Woonsan Ko wrote: > > We got errors when buildi