Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 42636 invoked from network); 18 Jan 2010 10:24:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Jan 2010 10:24:58 -0000 Received: (qmail 3657 invoked by uid 500); 18 Jan 2010 10:24:58 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 3578 invoked by uid 500); 18 Jan 2010 10:24:58 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 3568 invoked by uid 99); 18 Jan 2010 10:24:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2010 10:24:58 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [61.9.168.140] (HELO nskntmtas02p.mx.bigpond.com) (61.9.168.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2010 10:24:46 +0000 Received: from nskntotgx02p.mx.bigpond.com ([58.166.68.133]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20100118102422.OASX93.nskntmtas02p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com> for ; Mon, 18 Jan 2010 10:24:22 +0000 Received: from [10.0.0.10] (really [58.166.68.133]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20100118102421.ONTP5306.nskntotgx02p.mx.bigpond.com@[10.0.0.10]> for ; Mon, 18 Jan 2010 10:24:21 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: Schedules and Build Queues From: Brett Porter In-Reply-To: Date: Mon, 18 Jan 2010 21:24:21 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <11F274EF-3CF6-42C7-87AC-C02D8BFFE491@apache.org> References: <8667b1bd0904282105w2dfed8c2ha1a5adffe76691de@mail.gmail.com> <4A3CDC04.1020006@schulte.it> <4A3CF130.7030907@schulte.it> <4A42678C.2080000@schulte.it> To: dev@continuum.apache.org X-Mailer: Apple Mail (2.1077) X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150204.4B5436D6.005A,ss=1,fgs=0 X-Virus-Checked: Checked by ClamAV on apache.org On 16/01/2010, at 9:15 AM, Wendy Smoak wrote: > To improve this, I think > - there should be a single place to configure the feature +1 > - the user shouldn't have to create the queues, setting the number = should do it +1, though naming them is useful (using default names QUEUE_1, etc. to = make it quick if desired). If they are at least in one place that should = be ok. > - queues shouldn't belong to schedules (if queues are attached to > schedules, how do forced builds work?) It's at least the other way around (schedules assigned to queues, but = they certainly don't "belong" to schedules). But overall, I thought = everything was attached to build definitions, which seems the best place = here again. > I'd like to get this into JIRA but I'm struggling with whether to > paste what I wrote above with a summary of "Parallel Build > configuration is not intuitive" or whether it needs to be broken up. Either way works, since the above are fairly discrete two related = tickets is probably appropriate. - Brett -- Brett Porter brett@apache.org http://brettporter.wordpress.com/