continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Gruber (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-265) Concurrent builds
Date Wed, 27 Aug 2008 15:08:48 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146185#action_146185
] 

Christian Gruber commented on CONTINUUM-265:
--------------------------------------------

Never mind - I looked it up.  However, some of this could be resolved by allowing for any
projects that use different local repos to be potentially parallelized. Or asserting that
each group HAS its own local repo unless overridden, and allowing different groups to be parallel.
 

I know it's not that simple, because you need to manage thread pools and workers to do the
builds and such.

A bigger issue is that it requires a stronger build-order system than a forced linear ranking
based on dependency.  It would require a build tree where nodes could be pulled off and parallelized
and then some logic for finding the synchronization points.

> Concurrent builds
> -----------------
>
>                 Key: CONTINUUM-265
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-265
>             Project: Continuum
>          Issue Type: New Feature
>          Components: Core system
>            Reporter: Torsten Curdt
>             Fix For: 1.x
>
>
> Instead of processing the builds sequentially it would be great to be
> able to specify how many projects are being build concurrently.

-- 
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

        

Mime
View raw message