You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by "Harper, Brad" <br...@epsiia.com> on 2008/04/17 19:44:32 UTC
CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Continuum is set to build a maven project aggregating several <module>
sub-projects. In reality, the directory containing this top-level
project contains *many* more sub-projects than it's pom.xml describes.
When continuum build runs, it checks out the entire tree beneath this
main project, including all of the sub-directories associated with the
sub-projects that aren't specified in the pom. The activity checks out
far too much from the SCM repository than is necessary for the CI build
itself [as defined by the pom hierarchy] and adds tens of minutes to the
overall CI build time.
Suggestions on how to better control the behavior of the SCM checkout
performed by the continuum build? Thanks.
Brad
RE: CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Posted by "Harper, Brad" <br...@epsiia.com>.
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.
Brad
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Thursday, April 17, 2008 8:29 PM
> To: users@continuum.apache.org
> 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
> <br...@gmail.com> 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
>
Re: CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Posted by Wendy Smoak <ws...@gmail.com>.
On Thu, Apr 17, 2008 at 6:25 PM, Brett Porter <br...@gmail.com> 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
Re: CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Posted by Brett Porter <br...@gmail.com>.
On 18/04/2008, Harper, Brad <br...@epsiia.com> wrote:
> I'm sure its more complicated than this, but ...
Yes, it is :)
while -N is suitable in cases where the parent just has a pom.xml,
many projects include more files and subdirectories. Really what you
need to do is --exclude each module directory.
However, I have proposed in the past working all the modules from one
checkout. We're investigating those options.
Cheers,
Brett
>
> At one [high] level, it would seem that the scm plugin could check out
> the parent directory [only], and then check out the sub-directories
> corresponding to the aggregated sub-projects as described in the parent
> project's pom.
>
> And then proceed with the build lifecycle as usual.
>
>
> Brad
>
>
> > -----Original Message-----
> > From: Brett Porter [mailto:brett.porter@gmail.com]
> > Sent: Thursday, April 17, 2008 8:25 PM
> > To: users@continuum.apache.org
> > Subject: Re: CI Builds Need Only a Fraction of the
> > Sub-Projects in the SCM Repo
> >
>
> > 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.
> >
> > HTH,
> > Brett
> >
> > On 18/04/2008, Harper, Brad <br...@epsiia.com> wrote:
> > > Continuum is set to build a maven project aggregating
> > several <module>
> > > sub-projects. In reality, the directory containing this top-level
> > > project contains *many* more sub-projects than it's pom.xml
> > describes.
> > >
> > > When continuum build runs, it checks out the entire tree
> > beneath this
> > > main project, including all of the sub-directories
> > associated with the
> > > sub-projects that aren't specified in the pom. The activity
> > checks out
> > > far too much from the SCM repository than is necessary for the CI
> > > build itself [as defined by the pom hierarchy] and adds tens of
> > > minutes to the overall CI build time.
> > >
> > > Suggestions on how to better control the behavior of the
> > SCM checkout
> > > performed by the continuum build? Thanks.
> > >
> > >
> > > Brad
> > >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
RE: CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Posted by "Harper, Brad" <br...@epsiia.com>.
I'm sure its more complicated than this, but ...
At one [high] level, it would seem that the scm plugin could check out
the parent directory [only], and then check out the sub-directories
corresponding to the aggregated sub-projects as described in the parent
project's pom.
And then proceed with the build lifecycle as usual.
Brad
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Thursday, April 17, 2008 8:25 PM
> To: users@continuum.apache.org
> Subject: Re: CI Builds Need Only a Fraction of the
> Sub-Projects in the SCM Repo
>
> 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.
>
> HTH,
> Brett
>
> On 18/04/2008, Harper, Brad <br...@epsiia.com> wrote:
> > Continuum is set to build a maven project aggregating
> several <module>
> > sub-projects. In reality, the directory containing this top-level
> > project contains *many* more sub-projects than it's pom.xml
> describes.
> >
> > When continuum build runs, it checks out the entire tree
> beneath this
> > main project, including all of the sub-directories
> associated with the
> > sub-projects that aren't specified in the pom. The activity
> checks out
> > far too much from the SCM repository than is necessary for the CI
> > build itself [as defined by the pom hierarchy] and adds tens of
> > minutes to the overall CI build time.
> >
> > Suggestions on how to better control the behavior of the
> SCM checkout
> > performed by the continuum build? Thanks.
> >
> >
> > Brad
> >
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
Re: CI Builds Need Only a Fraction of the Sub-Projects in the SCM Repo
Posted by Brett Porter <br...@gmail.com>.
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.
HTH,
Brett
On 18/04/2008, Harper, Brad <br...@epsiia.com> wrote:
> Continuum is set to build a maven project aggregating several <module>
> sub-projects. In reality, the directory containing this top-level
> project contains *many* more sub-projects than it's pom.xml describes.
>
> When continuum build runs, it checks out the entire tree beneath this
> main project, including all of the sub-directories associated with the
> sub-projects that aren't specified in the pom. The activity checks out
> far too much from the SCM repository than is necessary for the CI build
> itself [as defined by the pom hierarchy] and adds tens of minutes to the
> overall CI build time.
>
> Suggestions on how to better control the behavior of the SCM checkout
> performed by the continuum build? Thanks.
>
>
> Brad
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/