You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "regis (JIRA)" <ji...@codehaus.org> on 2010/03/08 15:01:55 UTC
[jira] Created: (CONTINUUM-2481) Can not distribute project builds
from a same group.
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
[jira] Updated: (CONTINUUM-2481) Can not distribute project builds
from a same group.
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (CONTINUUM-2481) Can not distribute project
builds from a same group.
Posted by "regis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213071#action_213071 ]
regis commented on CONTINUUM-2481:
----------------------------------
I Wendy,
I use groups to seperate project by feature. In a group, some projects are related, but not all.
Of cours I could do the builds manually as you said but the objective is to do this automatically.
If I use a common (remote) repository in wich I deploy all the generated artifacts => every project is able to depend of the others.
Order of builds for related project is already supported by Continuum.
Example : Suppose I have 2 project : A and B. A depends of B.
==> I have to build B before A. If I call "deploy" instead of "install", B will be installed into the common repo.
==> I build A, the dependency B is downloaded from the common repo and Maven can build A.
No ?
Cheers,
Régis.
> 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
[jira] Commented: (CONTINUUM-2481) Can not distribute project
builds from a same group.
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ 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