Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <19178196.2921254813868674.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Tue, 6 Oct 2009 02:24:28 -0500 (CDT)
From: "Jevica Arianne B. Zurbano (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [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
In-Reply-To: 
 <12024144.3391253700427633.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ 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