Return-Path: 
 <issues-return-5179-apmail-continuum-issues-archive=continuum.apache.org@continuum.apache.org>
Delivered-To: apmail-continuum-issues-archive@www.apache.org
Received: (qmail 59847 invoked from network); 8 Mar 2010 14:31:41 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 8 Mar 2010 14:31:41 -0000
Received: (qmail 79260 invoked by uid 500); 8 Mar 2010 14:31:17 -0000
Delivered-To: apmail-continuum-issues-archive@continuum.apache.org
Received: (qmail 79236 invoked by uid 500); 8 Mar 2010 14:31:17 -0000
Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@continuum.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@continuum.apache.org>
List-Post: <mailto:issues@continuum.apache.org>
List-Id: <issues.continuum.apache.org>
Reply-To: dev@continuum.apache.org
Delivered-To: mailing list issues@continuum.apache.org
Received: (qmail 79228 invoked by uid 99); 8 Mar 2010 14:31:17 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 14:31:17 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com)
 (63.246.2.115)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 14:31:16 +0000
Received: from codehaus01.managed.contegix.com (localhost.localdomain
 [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id B439816000BD
	for <issues@continuum.apache.org>; Mon,  8 Mar 2010 08:30:55 -0600 (CST)
Date: Mon, 8 Mar 2010 08:30:55 -0600 (CST)
From: "Wendy Smoak (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Message-ID: 
 <20191260.102149.1268058655735.JavaMail.haus-jira@codehaus01.managed.contegix.com>
In-Reply-To: 
 <22260247.102105.1268056915155.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Subject: [jira] Commented: (CONTINUUM-2481) Can not distribute project
 builds from a same group.
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 4e90ceb663894a42f12c0e28abbab431


    [ 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