Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <11290721.1231555579910.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Fri, 9 Jan 2009 20:46:19 -0600 (CST)
From: "Maria Odea Ching (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Commented: (CONTINUUM-265) Concurrent builds
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Maria Odea Ching commented on CONTINUUM-265:
--------------------------------------------

Hi All,

I've staged another snapshot of the parallel builds branch (-r733009) at:

http://people.apache.org/~oching/continuum-parallel-builds-r733009/org/apache/continuum/continuum-jetty/1.3.1-SNAPSHOT/

To get it working:
1. In the Configuration page, set Number of Allowed Builds in Parallel to a value greater than 1 and save the changes.
2. Create a new Build Queue. You can create a few more if you want but you shouldn't be permitted to create more than the Number of Allowed Builds in Parallel you've set in the configuration.
3. In the Schedules page, edit DEFAULT_SCHEDULE and select the Build Queues you want to attach to it. These build queues would be used to distribute the checkouts/builds to be executed when a build is triggered (either forced or scheduled as long as the build definition used has the DEFAULT_SCHEDULE attached to it).
4. Add a number of projects (different project groups if possible) to Continuum. You should be able to see in the Queues page the current checkout/builds executing and the queued tasks, and to which Build Queue are these tasks executing or queued.

Step 3 is actually optional. If there are no build queues attached to a schedule, the parallel builds manager would use the DEFAULT_BUILD_QUEUE. But in order to demonstrate concurrent builds, we must attach multiple build queues to the schedule.

Comments, suggestions, feedback are welcome :)

If there are no major bugs found or no further changes in the implementation, I say we are ready to merge the branch to trunk..


> 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
>            Assignee: Maria Odea Ching
>             Fix For: 1.x
>
>         Attachments: continuum-265-docs.patch, CONTINUUM-265-UI.patch, continuum-265-webapp.patch, more-update-CONTINUUM-265-UI.patch, parallelBuilds-screenshots.zip, schedule-problem.patch, update-CONTINUUM-265-UI.patch
>
>
> 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