You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm@geronimo.apache.org by i386-redhat-linux-gnu <db...@apache.org> on 2005/07/09 12:59:31 UTC

build failed Sat Jul 9 03:59:30 PDT 2005

==[SUMMARY]====================================

BUILD FAILED

==[UPDATED]====================================




Re: Continuum and m2 (was Re: build failed Sat Jul...)

Posted by David Blevins <da...@visi.com>.
On Sun, Jul 10, 2005 at 12:19:15AM -0400, Jason van Zyl wrote:
> On Sat, 2005-07-09 at 18:23 -0700, David Blevins wrote:
> > On Sun, Jul 10, 2005 at 02:36:32AM +0200, Jacek Laskowski wrote:
> > > David Blevins wrote:
> > > 
> > > >>Yes, yes and yes.  Here is the source:
> > > >> http://codehaus.org/~dblevins/build/
> > > >>
> > > >
> > > >
> > > >Oh, and the suggestion in the past has been to have no attachments, just 
> > > >upload the logs to somewhere like http://geronimo.apache.org/build/<time> 
> > > >or something of the sort and just have a link in the email.
> > > 
> > > It sounds like some kind of CruiseControl's clone. I worked with CC in 
> > > the past and could set it up easily, but before doing so, I'd welcome 
> > > any comments if we should rely on CC or simply enhance Dave's script?
> > > 
> > 
> > My script is simple and dumb, really.  It's just a band-aid till we
> > can start using Continuum (*cough*, Jason).
> 
> Right now is it the build for the entire tree, or are you selectively
> building modules? 
> 
> There's an instance of Continuum in the Maven Zone
> (maven.zones.apache.org) and one at Codehaus that we could use.
> 
> We can chat in IRC about per module builds, scheduling of builds and
> whatever else but there really isn't any reason we can try it. Continuum
> works fine with m1/shell scripts too.
> 

Awesome.  I'll hit you on irc.

-David

Re: Continuum and m2 (was Re: build failed Sat Jul...)

Posted by Jason van Zyl <ja...@maven.org>.
On Sat, 2005-07-09 at 18:23 -0700, David Blevins wrote:
> On Sun, Jul 10, 2005 at 02:36:32AM +0200, Jacek Laskowski wrote:
> > David Blevins wrote:
> > 
> > >>Yes, yes and yes.  Here is the source:
> > >> http://codehaus.org/~dblevins/build/
> > >>
> > >
> > >
> > >Oh, and the suggestion in the past has been to have no attachments, just 
> > >upload the logs to somewhere like http://geronimo.apache.org/build/<time> 
> > >or something of the sort and just have a link in the email.
> > 
> > It sounds like some kind of CruiseControl's clone. I worked with CC in 
> > the past and could set it up easily, but before doing so, I'd welcome 
> > any comments if we should rely on CC or simply enhance Dave's script?
> > 
> 
> My script is simple and dumb, really.  It's just a band-aid till we
> can start using Continuum (*cough*, Jason).

Right now is it the build for the entire tree, or are you selectively
building modules? 

There's an instance of Continuum in the Maven Zone
(maven.zones.apache.org) and one at Codehaus that we could use.

We can chat in IRC about per module builds, scheduling of builds and
whatever else but there really isn't any reason we can try it. Continuum
works fine with m1/shell scripts too.

> :)
> 
> -David
> 
> 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

Three people can keep a secret provided two of them are dead.

 -- Unknown


Continuum and m2 (was Re: build failed Sat Jul...)

Posted by David Blevins <da...@visi.com>.
On Sun, Jul 10, 2005 at 02:36:32AM +0200, Jacek Laskowski wrote:
> David Blevins wrote:
> 
> >>Yes, yes and yes.  Here is the source:
> >> http://codehaus.org/~dblevins/build/
> >>
> >
> >
> >Oh, and the suggestion in the past has been to have no attachments, just 
> >upload the logs to somewhere like http://geronimo.apache.org/build/<time> 
> >or something of the sort and just have a link in the email.
> 
> It sounds like some kind of CruiseControl's clone. I worked with CC in 
> the past and could set it up easily, but before doing so, I'd welcome 
> any comments if we should rely on CC or simply enhance Dave's script?
> 

My script is simple and dumb, really.  It's just a band-aid till we
can start using Continuum (*cough*, Jason).

:)

-David


Re: build failed Sat Jul 9 03:59:30 PDT 2005

Posted by Jacek Laskowski <jl...@apache.org>.
David Blevins wrote:

>>Yes, yes and yes.  Here is the source:
>>  http://codehaus.org/~dblevins/build/
>>
> 
> 
> Oh, and the suggestion in the past has been to have no attachments, just upload the logs to somewhere like http://geronimo.apache.org/build/<time> or something of the sort and just have a link in the email.

It sounds like some kind of CruiseControl's clone. I worked with CC in 
the past and could set it up easily, but before doing so, I'd welcome 
any comments if we should rely on CC or simply enhance Dave's script?

> -David

Jacek


Re: build failed Sat Jul 9 03:59:30 PDT 2005

Posted by Dain Sundstrom <da...@iq80.com>.
+1

It would be nice if someone to whip up some perl code to pick out the  
most common failure messages.... normally that log is massive.

-dain

On Jul 9, 2005, at 12:16 PM, Aaron Mulder wrote:

> On Sat, 9 Jul 2005, David Blevins wrote:
>
>> Oh, and the suggestion in the past has been to have no  
>> attachments, just
>> upload the logs to somewhere like
>> http://geronimo.apache.org/build/<time> or something of the sort and
>> just have a link in the email.
>>
>
> +1  :)
>
> Aaron
>


Re: build failed Sat Jul 9 03:59:30 PDT 2005

Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On Sat, 9 Jul 2005, David Blevins wrote:
> Oh, and the suggestion in the past has been to have no attachments, just
> upload the logs to somewhere like
> http://geronimo.apache.org/build/<time> or something of the sort and
> just have a link in the email.

+1  :)

Aaron

Re: build failed Sat Jul 9 03:59:30 PDT 2005

Posted by David Blevins <da...@visi.com>.
On Sat, Jul 09, 2005 at 12:08:22PM -0700, David Blevins wrote:
> On Sat, Jul 09, 2005 at 08:49:48AM -0400, Aaron Mulder wrote:
> > 	So I got this message.  I looked at the attachment, and the very 
> > bottom said build succeeded.  I guess that means that there are several 
> > build outputs glommed into one attachment and there was a failure 
> > somewhere in the middle?  If that's true can we break up the attachment or 
> > even better only attach the output of the step that failed?
> 
> 
> Yes, yes and yes.  Here is the source:
>   http://codehaus.org/~dblevins/build/
> 

Oh, and the suggestion in the past has been to have no attachments, just upload the logs to somewhere like http://geronimo.apache.org/build/<time> or something of the sort and just have a link in the email.

-David

Re: build failed Sat Jul 9 03:59:30 PDT 2005

Posted by David Blevins <da...@visi.com>.
On Sat, Jul 09, 2005 at 08:49:48AM -0400, Aaron Mulder wrote:
> 	So I got this message.  I looked at the attachment, and the very 
> bottom said build succeeded.  I guess that means that there are several 
> build outputs glommed into one attachment and there was a failure 
> somewhere in the middle?  If that's true can we break up the attachment or 
> even better only attach the output of the step that failed?


Yes, yes and yes.  Here is the source:
  http://codehaus.org/~dblevins/build/

-David

Re: build failed Sat Jul 9 03:59:30 PDT 2005

Posted by Aaron Mulder <am...@alumni.princeton.edu>.
	So I got this message.  I looked at the attachment, and the very 
bottom said build succeeded.  I guess that means that there are several 
build outputs glommed into one attachment and there was a failure 
somewhere in the middle?  If that's true can we break up the attachment or 
even better only attach the output of the step that failed?

Thanks,
	Aaron

On Sat, 9 Jul 2005, i386-redhat-linux-gnu wrote:
> ==[SUMMARY]====================================
> 
> BUILD FAILED
> 
> ==[UPDATED]====================================
> 
> 
> 
>