You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2010/03/17 22:50:23 UTC
[jira] Updated: (CONTINUUM-2481) Can not distribute project builds
from a same group.
[ http://jira.codehaus.org/browse/CONTINUUM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-2481:
-----------------------------------
Fix Version/s: Backlog
> 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 (Beta)
> Environment: Maven 2.1.0-M1 / Continuum 1.3.4 using distributed builds.
> Reporter: regis
> Priority: Critical
> Fix For: Backlog
>
>
> 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