continuum project list page listing projects in error when they are successful

2006-06-27 Thread Baron Reznik
Hi,

I have continuum set up building a multimodule set of poms with 100+
projects in total. I've noticed that on the continuum home page, some of
the projects will mysteriously, and seemingly randomly switch from a
'build success' to 'build error' state, even when the builds are
passing. If I click on the build error X, I'm taken to the project info
page which lists the project in a 'build success' state.

I'm not even sure where to start with what could be causing these
erroneous build errors, but it would certainly be a lot nicer and
comforting to see the homepage list all the projects with the accurate
build state.

Thanks,
Baron


Re: Subversion post-commit hook

2006-06-13 Thread Baron Reznik
On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
> On 6/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > I know I'd find this useful as well, for several reasons:
> > -If you simply let continuum build every 5 mins, there could potentially be 
> > more than 1 commit during that time, and you would be building multiple 
> > revisions worth of changes. Ideally, you would want to build once/revision 
> > so if the build breaks, you know which commit broke it.
> 
> 
> You are not considering here the time that it takes to build the project.
> a commits
> continuum starts building
> b commits
> continuum can't start building, busy
> c commits
> continuum can't start building, busy
> continuum finishes building
> continuum starts building b and c changes
> 
> 

^^^ That's exactly what I'm talking about. Sometimes it will build 1
revision, and other times 2 or more revisions could be mixed into one
build. I'd like to avoid that. 

> 
> > -The continuum server would not be making as many hits to the svn server. 
> > If you're building dozens and dozens of projects, this adds up when it's 
> > once every 5 mins.
> 
> I don't realy know what is the overhead of getting the revision number
> to check for changes but shouldn't be heavy at all
> 

I don't know how you verify this, but I got the impression that
continuum was performing a 'svn update' (for subversion, anyways),
which, could be rather heavy depending on how your repository is laid
out. I'm not sure offhand if subversion provides a more efficient way
though.

> >
> > If you got rather fancy, it would sure be nice to have the commit check if 
> > there were new projects added, and automagically add them to continuum as 
> > well.
> >
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] on behalf of Carlos Sanchez
> > Sent: Thu 6/8/2006 1:54 PM
> > To: continuum-users@maven.apache.org
> > Subject: Re: Subversion post-commit hook
> >
> > why do you need that, setting a short period like 5 min is not enough?
> >
> > On 6/8/06, Chris Wall <[EMAIL PROTECTED]> wrote:
> > > We'd like to trigger Continuum builds upon developer commits in
> > > Subversion.  It sounds like to do so we need to develop an xml-rpc
> > > client.
> > >
> > > Has anyone developed a post-commit hook into Continuum from Subversion?
> > > Is there related documentation available?
> > >
> > > Thanks.
> > >
> > > -Chris
> > >
> > >
> > > ___
> > > Notice:  This email message, together with any attachments, may contain
> > > information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> > > entities,  that may be confidential,  proprietary,  copyrighted  and/or
> > > legally privileged, and is intended solely for the use of the individual
> > > or entity named in this message. If you are not the intended recipient,
> > > and have received this message in error, please immediately return this
> > > by email and then delete it.
> > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> >  -- The Princess Bride
> >
> >
> 
>