You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benjamin Bentmann <be...@udo.edu> on 2008/07/30 15:13:53 UTC

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

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 are not that tightly coupled, might it 
be sensible to change the build to "fail-at-end" to still get IT results 
for the other modules? What do you think?


Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Jason van Zyl <ja...@maven.org>.
+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 are not that tightly coupled,  
> might it be sensible to change the build to "fail-at-end" to still  
> get IT results for the other modules? What do you think?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

What matters is not ideas, but the people who have them. Good people  
can fix bad ideas, but good ideas can't save bad people.

  -- Paul Graham


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Arnaud HERITIER <ah...@gmail.com>.
ok for me.
I completly forgot the -fae option in maven. :-)



On Wed, Jul 30, 2008 at 7:15 PM, Brian Fox <br...@infinity.nu> 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, at 9:36 AM, "Arnaud HERITIER" <ah...@gmail.com>
> 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
>> builds with -Dmaven.repo.local=...
>> Perhaps we could use the "Use private maven repository" option that was
>> added in 1.223 ?
>>
>> We have also always one executor frozen for 1 day :
>> maven-ant-plugin-trunk<
>> https://ci.sonatype.org/job/maven-ant-plugin-trunk/>
>>
>> Cheers,
>>
>> On Wed, Jul 30, 2008 at 3:13 PM, Benjamin Bentmann <
>> benjamin.bentmann@udo.edu> 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 are not that tightly coupled, might it
>>> be
>>> sensible to change the build to "fail-at-end" to still get IT results for
>>> the other modules? What do you think?
>>>
>>>
>>> Benjamin
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
>> --
>> ..........................................................
>> Arnaud HERITIER
>> ..........................................................
>> OCTO Technology - aheritier AT octo DOT com
>> www.octo.com | blog.octo.com
>> ..........................................................
>> ASF - aheritier AT apache DOT org
>> www.apache.org | maven.apache.org
>> ...........................................................
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

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

Posted by Brian Fox <br...@infinity.nu>.
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" <ah...@gmail.com>  
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
> builds with -Dmaven.repo.local=...
> Perhaps we could use the "Use private maven repository" option that  
> was
> added in 1.223 ?
>
> We have also always one executor frozen for 1 day :
> maven-ant-plugin-trunk<https://ci.sonatype.org/job/maven-ant-plugin-trunk/ 
> >
>
> Cheers,
>
> On Wed, Jul 30, 2008 at 3:13 PM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> 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 are not that tightly coupled,  
>> might it be
>> sensible to change the build to "fail-at-end" to still get IT  
>> results for
>> the other modules? What do you think?
>>
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> -- 
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Brian Fox <br...@infinity.nu>.
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 <ja...@maven.org> 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 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 ?
>>
>> We have also always one executor frozen for 1 day :
>> maven-ant-plugin-trunk<https://ci.sonatype.org/job/maven-ant-plugin-trunk/ 
>> >
>>
>> Cheers,
>>
>> On Wed, Jul 30, 2008 at 3:13 PM, Benjamin Bentmann <
>> benjamin.bentmann@udo.edu> 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 are not that tightly coupled,  
>>> might it be
>>> sensible to change the build to "fail-at-end" to still get IT  
>>> results for
>>> the other modules? What do you think?
>>>
>>>
>>> Benjamin
>>>
>>> --- 
>>> ------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> -- 
>> ..........................................................
>> Arnaud HERITIER
>> ..........................................................
>> OCTO Technology - aheritier AT octo DOT com
>> www.octo.com | blog.octo.com
>> ..........................................................
>> ASF - aheritier AT apache DOT org
>> www.apache.org | maven.apache.org
>> ...........................................................
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> We all have problems. How we deal with them is a measure of our worth.
>
> -- Unknown
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Jason van Zyl <ja...@maven.org>.
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
> builds with -Dmaven.repo.local=...
> Perhaps we could use the "Use private maven repository" option that  
> was
> added in 1.223 ?
>
> We have also always one executor frozen for 1 day :
> maven-ant-plugin-trunk<https://ci.sonatype.org/job/maven-ant-plugin-trunk/ 
> >
>
> Cheers,
>
> On Wed, Jul 30, 2008 at 3:13 PM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> 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 are not that tightly coupled,  
>> might it be
>> sensible to change the build to "fail-at-end" to still get IT  
>> results for
>> the other modules? What do you think?
>>
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> -- 
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

We all have problems. How we deal with them is a measure of our worth.

  -- Unknown


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yep, fixed that. The deadlock on the wrong jdk must be new in the
updated Hudson.

-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu] 
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:

> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Benjamin Bentmann <be...@udo.edu>.
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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Fixed now, never seen that happen before so I'll keep an eye out. 

-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu] 
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 have also always one executor frozen for 1 day :
>
maven-ant-plugin-trunk<https://ci.sonatype.org/job/maven-ant-plugin-trun
k/>

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 builds in its queue...


Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Benjamin Bentmann <be...@udo.edu>.
Arnaud HERITIER wrote:

> We have also always one executor frozen for 1 day :
> maven-ant-plugin-trunk<https://ci.sonatype.org/job/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 builds in its queue...


Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


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

Posted by Arnaud HERITIER <ah...@gmail.com>.
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 ?

We have also always one executor frozen for 1 day :
maven-ant-plugin-trunk<https://ci.sonatype.org/job/maven-ant-plugin-trunk/>

Cheers,

On Wed, Jul 30, 2008 at 3:13 PM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> 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 are not that tightly coupled, might it be
> sensible to change the build to "fail-at-end" to still get IT results for
> the other modules? What do you think?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

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

Posted by Brian Fox <br...@infinity.nu>.
Go for it

Sent from my iPhone

On Jul 30, 2008, at 9:13 AM, Benjamin Bentmann <benjamin.bentmann@udo.edu 
 > 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 are not that tightly coupled,  
> might it be sensible to change the build to "fail-at-end" to still  
> get IT results for the other modules? What do you think?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org