Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: domain of oching@exist.com designates
 74.125.46.152 as permitted sender)
Message-ID: <1a57a2980812181905r7e2d6d21kbfde5e20f0d5cd70@mail.gmail.com>
Date: Fri, 19 Dec 2008 11:05:21 +0800
From: "Maria Odea Ching" <oching@apache.org>
Sender: oching@exist.com
To: dev@continuum.apache.org
Subject: Initial Efforts for Parallel Builds
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_34911_28767255.1229655921061"

------=_Part_34911_28767255.1229655921061
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Everyone,

I've staged a snapshot from the parallel builds branch to give you a preview
of the recent efforts that have been put into this.
You can get the binaries @
http://people.apache.org/~oching/continuum-parallel-builds/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 the DEFAULT_SCHEDULE is used.
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.

There are still a couple of bugs that need to be fixed before we're ready to
merge to trunk:
1. checkboxes for cancelling a set of queued tasks in Queues page are not
showing up
2. handle instances when a project is still building and a release is
triggered
3. deletion of build queue (a FK constraint violation error is encountered)
4. fix failing tests due to a number methods of some classes in handling the
task queues being moved

Thoughts, comments, suggestions and feedback (good or bad) are very welcome
;-)


Thanks,
Deng


-- 
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

------=_Part_34911_28767255.1229655921061--