[ http://jira.codehaus.org/browse/CONTINUUM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213057#action_213057 ] 

Wendy Smoak commented on CONTINUUM-2481:
----------------------------------------

I'm curious, are the projects in your group related?  Are they all part of one large multi-module project?

You could probably do it manually by selecting some projects using the checkboxes and choosing a different build definition (which has a build environment which contains the build agent group).

However, the question of automatically splitting up a multi-module build (or even a group of unrelated projects) is fairly complex.  I don't think this has been tackled yet in Continuum.

> Can not distribute project builds from a same group.
> ----------------------------------------------------
>
>                 Key: CONTINUUM-2481
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2481
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Distributed Builds
>    Affects Versions: 1.3.4
>         Environment: Maven 2.1.0-M1 / Continuum 1.3.4 using distributed builds.
>            Reporter: regis
>            Priority: Critical
>
> At the moment, if a group build is launched, all project from the group are distributed to the same build agent.
> This rule makes the distributed builds process ineffective if we have a few groups containing a lot of project.
> Splitting the groups does not make sense because we must not considere some technical limits into a functionnal feature.
> We can use a common maven repository that could be configured into a maven profile, and instead of calling "install", we call "deploy" using this profil :
> "mvn -P<integration> clean deploy"
> Then, all the artifacts from any build agent will be deployed into the same maven repository. So all projects are available for any other and at any time.
> The user should be able to build a group AND to choice the distribution mode of the builds.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira