[
http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated CONTINUUM-2368:
------------------------------------
Fix Version/s: 1.3.5
sched for 1.3.5 either to fix or close out as not reproducible
> Build queues attached to the schedule are removed from when the schedule is
> triggered, only the default build queue is being retained and used instead
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2368
> URL: http://jira.codehaus.org/browse/CONTINUUM-2368
> Project: Continuum
> Issue Type: Bug
> Components: Web - UI
> Affects Versions: 1.3.4
> Reporter: Maria Odea Ching
> Fix For: 1.3.5
>
>
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
