You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2009/09/23 12:07:07 UTC
[jira] Created: (CONTINUUM-2368) Build queues attached to the
schedule are sometimes not shown correctly in the Schedules page
Build queues attached to the schedule are sometimes not shown correctly in the Schedules page
---------------------------------------------------------------------------------------------
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
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 affecting the build queue name displayed in the Queues page. Some of the projects are still actually building in SECOND_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
[jira] Commented: (CONTINUUM-2368) 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
Posted by "Jevica Arianne B. Zurbano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193663#action_193663 ]
Jevica Arianne B. Zurbano commented on CONTINUUM-2368:
------------------------------------------------------
This issue seems not reproducible in r822129.
The projects were distributed to the 2 build queues attached to the schedule being used.
This happens on both forced and scheduled builds.
And, the build queues are still attached to the schedule.
> 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
[jira] Updated: (CONTINUUM-2368) Build queues attached to the
schedule are sometimes not shown correctly in the Schedules page
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated CONTINUUM-2368:
----------------------------------------
Description:
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.
was:
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 affecting the build queue name displayed in the Queues page. Some of the projects are still actually building in SECOND_BUILD_QUEUE but instead of showing SECOND_BUILD_QUEUE for the Build Queue name, it's showing DEFAULT_BUILD_QUEUE.
> Build queues attached to the schedule are sometimes not shown correctly in the Schedules page
> ---------------------------------------------------------------------------------------------
>
> 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
>
> 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
[jira] Commented: (CONTINUUM-2368) Build queues attached to the
schedule are sometimes not shown correctly in the Schedules page
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191939#action_191939 ]
Maria Odea Ching commented on CONTINUUM-2368:
---------------------------------------------
It looks like the build queues attached to the schedule are only being removed when the schedule is triggered. I forced the builds a number of times and both build queues were utilized.
> Build queues attached to the schedule are sometimes not shown correctly in the Schedules page
> ---------------------------------------------------------------------------------------------
>
> 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
>
> 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
[jira] Closed: (CONTINUUM-2368) 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
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan closed CONTINUUM-2368.
------------------------------------------
Resolution: Cannot Reproduce
> 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
[jira] Updated: (CONTINUUM-2368) 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
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated CONTINUUM-2368:
----------------------------------------
Summary: 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 (was: Build queues attached to the schedule are sometimes not shown correctly in the Schedules page)
updating summary to correctly reflect the problem
> 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
>
> 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
[jira] Updated: (CONTINUUM-2368) 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
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (CONTINUUM-2368) Build queues attached to the
schedule are sometimes not shown correctly in the Schedules page
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191938#action_191938 ]
Maria Odea Ching commented on CONTINUUM-2368:
---------------------------------------------
If someone else is able to reproduce this issue, I think this needs to be fixed in 1.3.5 as it is a regression.
> Build queues attached to the schedule are sometimes not shown correctly in the Schedules page
> ---------------------------------------------------------------------------------------------
>
> 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
>
> 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
[jira] Updated: (CONTINUUM-2368) 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
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-2368:
-----------------------------------
Fix Version/s: (was: 1.3.5)
Removing fix-for version so it won't show up in the release notes.
> 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
>
> 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
[jira] Commented: (CONTINUUM-2368) Build queues attached to the
schedule are sometimes not shown correctly in the Schedules page
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191937#action_191937 ]
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 page
> ---------------------------------------------------------------------------------------------
>
> 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
>
> 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
[jira] Commented: (CONTINUUM-2368) 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
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191942#action_191942 ]
Maria Odea Ching commented on CONTINUUM-2368:
---------------------------------------------
I don't see this happening in vmbuild though..
> 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
>
> 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
[jira] Commented: (CONTINUUM-2368) 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
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192996#action_192996 ]
Maria Catherine Tan commented on CONTINUUM-2368:
------------------------------------------------
It works for me using 1.3.5 r820489.
Here's what I did:
1. enabled parallel builds
2. added 2 build queues, SECOND_BUILD_QUEUE, THIRD_BUILD_QUEUE
3. added SECOND_BUILD_QUEUE and THIRD_BUILD_QUEUE to the Default Schedule
4. added 3 projects to different project groups
5. Forced build all projects
Result -> all three project groups were distributed to the three build queues
6. Set their build definition to "Always Build"
7. Scheduled build
Result -> all three project groups were distributed to the three build queues
8. Edit default schedule
Result -> all build queues are still attached to the schedule
> 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