RE: CI job maven-shared: fail-at-end?

Yep, fixed that. The deadlock on the wrong jdk must be new in the updated Hudson. -Original Message- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 4:15 AM To: Maven Developers List Subject: Re: CI job maven-shared: fail-at-end? Brian E. Fox wrote

Re: CI job maven-shared: fail-at-end?

Brian E. Fox wrote: Fixed now, never seen that happen before so I'll keep an eye out. Thanks! Can you also have a look at https://ci.sonatype.org/job/maven-2.0.10-RC/2/console I assume the job needs to be reconfigured to use Java 1.5 or each build will deadlock again. Benjamin

Re: CI job maven-shared: fail-at-end?

ok for me. I completly forgot the -fae option in maven. :-) On Wed, Jul 30, 2008 at 7:15 PM, Brian Fox <[EMAIL PROTECTED]> wrote: > Just add -fae to the goals line. Until I verify the use separate repo works > I prefer to use the maven switch directly > > Sent from my iPhone > > On Jul 30, 2008

Re: CI job maven-shared: fail-at-end?

Just add -fae to the goals line. Until I verify the use separate repo works I prefer to use the maven switch directly Sent from my iPhone On Jul 30, 2008, at 9:36 AM, "Arnaud HERITIER" <[EMAIL PROTECTED]> wrote: Is it possible ? I never saw this option in hudson. Is it the option called "

Re: CI job maven-shared: fail-at-end?

Go for it Sent from my iPhone On Jul 30, 2008, at 9:13 AM, Benjamin Bentmann <[EMAIL PROTECTED] > wrote: Hi, while having a look at the recent failure during build #181 of maven- shared, I noticed that the modules after the failing one were not build at all ("Build failed before it gets

Re: CI job maven-shared: fail-at-end?

No, it's not required to redo it as freestyle just to add fae On Jul 30, 2008, at 9:45 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: Just use a freestyle project and then you can do whatever you like. On 30-Jul-08, at 6:36 AM, Arnaud HERITIER wrote: Is it possible ? I never saw this option in

RE: CI job maven-shared: fail-at-end?

Fixed now, never seen that happen before so I'll keep an eye out. -Original Message- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2008 3:37 PM To: Maven Developers List Subject: Re: CI job maven-shared: fail-at-end? Arnaud HERITIER wrote: > We h

Re: CI job maven-shared: fail-at-end?

Arnaud HERITIER wrote: We have also always one executor frozen for 1 day : maven-ant-plugin-trunk Seems like the other build processor has also gone mad with "maven-2.0.10-RC" :( Hudson is totally blocked and has already seven new IT build

Re: CI job maven-shared: fail-at-end?

Just use a freestyle project and then you can do whatever you like. On 30-Jul-08, at 6:36 AM, Arnaud HERITIER wrote: Is it possible ? I never saw this option in hudson. Is it the option called "Build modules in parallel" ? I also noticed that we oftened manually defined custom local repos for

Re: CI job maven-shared: fail-at-end?

Is it possible ? I never saw this option in hudson. Is it the option called "Build modules in parallel" ? I also noticed that we oftened manually defined custom local repos for builds with -Dmaven.repo.local=... Perhaps we could use the "Use private maven repository" option that was added in 1.223

Re: CI job maven-shared: fail-at-end?

+1 On 30-Jul-08, at 6:13 AM, Benjamin Bentmann wrote: Hi, while having a look at the recent failure during build #181 of maven- shared, I noticed that the modules after the failing one were not build at all ("Build failed before it gets to this module"). Since the modules of maven-shared