continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Odea Ching (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-2368) Build queues attached to the schedule are sometimes not shown correctly in the Schedules page
Date Wed, 23 Sep 2009 10:17:06 GMT


Maria Odea Ching commented on CONTINUUM-2368:

I notice this happening everytime the schedule is triggered. I would notice in the Queues
page that all the projects are building in only one queue eventhough I already attached two
queues to the schedule a number of times. If I force build the projects right after attaching
the SECOND_BUILD_QUEUE to the default schedule again, the two build queues are utilized.

> Build queues attached to the schedule are sometimes not shown correctly in the Schedules
> ---------------------------------------------------------------------------------------------
>                 Key: CONTINUUM-2368
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Web - UI
>    Affects Versions: 1.3.4
>            Reporter: Maria Odea Ching
> You must enable parallel builds first then create a new Build Queue named SECOND_BUILD_QUEUE.
Attach SECOND_BUILD_QUEUE to the Default Schedule, this should result to both the Default
Build Queue and SECOND_BUILD_QUEUE to be attached to the Default Schedule. Save the changes.
Now build multiple project groups using their build definitions attached to the Default Schedule.
After a while, edit the Default Schedule again. You will see in the UI that only the Default
Build Queue is attached to the schedule.
> I think this is also sometimes affecting the build queue name displayed in the Queues
page. Some of the projects are still actually building in SECOND_BUILD_QUEUE (sometimes they're
all building in the Default Build Queue) but instead of showing SECOND_BUILD_QUEUE for the
Build Queue name, it's showing DEFAULT_BUILD_QUEUE.

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