continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harper, Brad" <>
Subject RE: CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Date Fri, 18 Apr 2008 02:08:36 GMT
We check out the top-level aggregate pom, and then check out each of
necessary sub-project's individually. It isn't until very recently that
we've attempted to automate these builds, hence the use of continuum.

I should note that the other projects under the top-level directory [not
being included in the CI build] are a mixed bag of things, but share the
<dependencyManagement> described by their common parent, as well as the
configuration for plugins, e.g. maven-war-plugin.

The projects that we're attempting to include in the CI builds produce
the core jars and war files that other projects in turn use. In the more
complicated cases, these other projects are war overlays and they're
built as-needed in a disjoint fashion from within an IDE.


> -----Original Message-----
> From: Wendy Smoak [] 
> Sent: Thursday, April 17, 2008 8:29 PM
> To:
> Subject: Re: CI Builds Need Only a Fraction of the 
> Sub-Projects in the SCM Repo
> On Thu, Apr 17, 2008 at 6:25 PM, Brett Porter 
> <> wrote:
> > We're looking to propose something for a future version to improve  
> > this behaviour.
> >
> >  At the moment, you have another alternative in that you 
> can use the  
> > checkbox on addition that runs the build as one checkout 
> instead of  
> > separate modules.
> Doing it as a single recursive build wouldn't solve the 
> problem of it checking out all the subdirectories...
> Leaving Continuum out of it, how would you do this using your 
> scm client alone?
> --
> Wendy

View raw message