Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <46FBFCDA.4030604@venisse.net>
Date: Thu, 27 Sep 2007 20:56:26 +0200
From: Emmanuel Venisse <emmanuel@venisse.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: continuum-users@maven.apache.org
Subject: Re: When builds are done in multi-module projects ?
References: <fc82b4040709240227r71b781f2g4352ca09cd337b81@mail.gmail.com>
	 <fc82b4040709240709x4a352f1ekcfa9b3b6e906b351@mail.gmail.com>
	 <46F7C6D3.6030800@venisse.net>
	 <fc82b4040709250119v418015cdx14035f89c2b973cf@mail.gmail.com>
	 <46F8CD17.1010304@venisse.net>
	 <fc82b4040709260515h1074ccb2kf5b3d2296ee12f3b@mail.gmail.com>
	 <46FA514B.4010702@venisse.net>
	 <fc82b4040709260649x29dc92a5t16316000a38ebb51@mail.gmail.com>
	 <46FA67E2.2080200@venisse.net>
	 <fc82b4040709260745k3fa43635n63a37c65ef4eef88@mail.gmail.com>
 <fc82b4040709270857r5954d8ecy17a02c071cbbccb1@mail.gmail.com>
In-Reply-To: <fc82b4040709270857r5954d8ecy17a02c071cbbccb1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

It isn't recommended to have the same source tree twice in continuum if pom files have the same version.
With this configuration, continuum can't resolve correctly the build order so a project B that must be built after an other project A is built before, then when A is built, Continuum detect a change 
on it and build B

Emmanuel

Damien Lecan a �crit :
>> I will reinit all my Continuum instance (fresh database, fresh
>> checkout), activate scm debug and see what happen later.
>>
>> I will plan 2 build definitions :
>>  1. run clean deploy every even hours
>>  2. run clean deploy site-deploy every odd hours
> 
> Ok, here are the results.
> I ran concurrently another checkout of my project, but this one built
> by only one build definition.
> 
> To summarize :
> 
> Group Project 1
>  1. every even hours : clean deploy
>  2. every odd hours : clean deploy site-deploy
> 
> Group Project 2 (same project as above = same sources)
>  1. every hours : clean deploy site-deploy
> 
> After 21 hours, results :
> 
>                               GP1                GP2
> build status          all success      all success
> nb of BD exec           21*                  21
> number of build       2->18**                1
> 
> * : BP1 for GP1 was executed 11 times when BP2 was executed 10 times
> (=21 executions)
> 
> ** : the 25 modules of my project where not built all together for each build.
> Parent project was built twice, when the final module (depends on each
> other modules) was built 18 times. All other modules ware built
> between 3 and 17 times, depending on their dependency configurations.
> 
> What can be deducted from theses tests ?
>  - Several build definitions for the same project group produces
> unnecessary builds, without any source modification
> 
>  => Maybe build execution doesn't check previous executions of all
> other build definitions for the same project group
> 
> What do you think ?
> 
> Thanks
> 
> Damien Lecan
> 
>