Hi
   There will be alternatives in bamboo level, such as we can control the
building process* via the dependency management*, the solution will work as
follows
          1.  Once the first job finishes all the product jobs starts
running.
                   means as Pradeep mention the target * (**mvn clean
install -Dbamboo=build) *will run first
          2. There after we will config different planes for individual
products (but will not run simultaneous).
                   e.g : assume, it will start to Build ESB first then will
start IS to build ( means at ESB Bamboo build plan level  we can
configure dependencies such as ,
                             under the manual dependency management we can
say the child plan next to be executed there will select IS as child plan *(BUT
it will not run till ESB maven goals are finish -regardless of success or
not) *that configuration can be done at under the *
dependency blocking Strategy* where we will select (*Block build if parent
builds are queued or in progress-If parent builds are queued or building,
the current build will be blocked.)*
*            3* Like wise at each product level we need to decide the next
child product to build regardless of success or failure.
               I think this solution might overcome the port biding issue
 WDYT ?

cheers
Dushan

On Tue, Jan 3, 2012 at 3:23 PM, Afkham Azeez <[email protected]> wrote:

> There is another problem in running all the product builds in parallel on
> the same machine; integration tests will fail due to port binding
> exceptions. To overcomes this, we need to change the integration tests in
> each product to start servers with portoffsets unique to each product.
>
>
> On Tue, Jan 3, 2012 at 3:15 PM, Afkham Azeez <[email protected]> wrote:
>
>> -1. That breaks the one-checkout & one-build concept. The building by
>> parts is fine, but building from the root pom level is also essential. If
>> we don't do that, we will never know when the one-checkout one-build fails.
>> Basically, once this stabilization is done, there can be no failures at
>> product level, and if new failures are introduced, they should be fixed
>> ASAP.
>>
>> On Tue, Jan 3, 2012 at 3:09 PM, Pradeep Fernando <[email protected]>wrote:
>>
>>> Hi all,
>>>
>>> Had a chat with Dushan. Now we are building the carbon source from the
>>> root pom. The build is almost woking fine. (it fails at the product level).
>>>
>>> The problem with this setup is, even though some products are building
>>> fine, it has dependencies among product builds.
>>>
>>> Ex. due to a docGen issue in ESB product, all the subsequent product
>>> builds get failed. (no packs)
>>>
>>> IMHO, correct way to do this is,
>>>
>>> *build carbon-source up-to features using a one build job
>>> *create individual build jobs per each product.
>>> * Once the first job finishes all the product jobs starts running.
>>> (parallel)
>>>
>>> Dushan is trying this out in the Bamboos server.
>>>
>>>
>>> we can use a bamboo profile to build carbon up to features (first-job).
>>> - (so we dont have to comment out product builds from root pom)
>>>
>>> thanks,
>>> --Pradeep
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Dushan Abeyruwan
WSO2 Inc
Software Engineer

Mobile:(+94)714408632
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to