continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "deckrider (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-265) Concurrent builds
Date Sat, 10 Jan 2009 14:58:19 GMT


deckrider commented on CONTINUUM-265:

Thank you.  I am trying this.  But I'm confused with respect to this:

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

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.

I see my default queue and additional queue when I edit default schedule.  But I don't see
how to select both to add.  I've tried shift click, etc.  and then save, but the log does
not appear to show that I've selected them.

Also how is this optional if one wants to have parallel builds?

Finally, how does this interact with the local repository?  Is it expected that we must set
up a repository for each queue to avoid potential corruption?  If so, why not make the UI
reflect this and simplify setup?

> Concurrent builds
> -----------------
>                 Key: CONTINUUM-265
>                 URL:
>             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,, schedule-problem.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:
For more information on JIRA, see:


View raw message