Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: domain of wsmoak@gmail.com designates
 74.125.92.145 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=v98rCZBXI4xz5HpptUwmmGEHjAcIpgdSUI8lNPbk/7gyuhkbeRGnkpdG+/J6pzPZBR
         LnED0VbRsFMphTD8mrS2TX2Xk+LSkwXPjN5MegQcD5Zaim8NjrLM6Wc1O44qrFU+S+v2
         xZH7vGv+X8QfPYrpSJiw+BM94GIkyWnHtmFEY=
MIME-Version: 1.0
In-Reply-To: <8667b1bd0904282105w2dfed8c2ha1a5adffe76691de@mail.gmail.com>
References: <adba96190903131858j822b82h7ca4256b362ad3f9@mail.gmail.com>
	<adba96190904280651y54c95668m94fa5a95925be655@mail.gmail.com>
	<8667b1bd0904282105w2dfed8c2ha1a5adffe76691de@mail.gmail.com>
From: Wendy Smoak <wsmoak@gmail.com>
Date: Fri, 19 Jun 2009 18:34:12 -0700
Message-ID: <adba96190906191834o47cd540em858da39302bfa46c@mail.gmail.com>
Subject: Re: Schedules and Build Queues
To: dev@continuum.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So... I've thought about this, tried to explain it in presentations
about Continuum, and talked to users about it.

The most devastating comment I heard was from someone who has tried
Continuum on and off since the early days who said, "You've added a
lot of complexity."

IMO, the additional control is not worth the added complexity.

It would be different if we'd implemented the simple case first and
had people complaining that they need to do X.  But so far, I haven't
met anyone who understands how this works.  (I'm not exactly clear
what happens with the queues you *don't* attach to a schedule.  And if
queues are attached to schedules, then what about forced builds?)

I think we should remove the 'number of builds allowed in parallel'
from the general configuration screen, and just have some queues.
More queues, more builds can happen in parallel.

Let's see what people think here, then I may float the idea in the
user list to get feedback.

--=20
Wendy

On Tue, Apr 28, 2009 at 9:05 PM, Deng Ching<oching@apache.org> wrote:
> Hi Wendy,
>
> (Sorry for the very late reply :)
>
> The Build Queues were attached to a Schedule so as to give some control o=
ver
> where or in which build queues projects are/can be built.
> Users can also control the number of build queues running for every fired
> schedule. If the schedule and build queues were totally separate, users
> won't have
> this form of control..
>
> Thanks,
> Deng
>
> On Tue, Apr 28, 2009 at 9:51 PM, Wendy Smoak <wsmoak@gmail.com> wrote:
>
>> ping?
>>
>> On Fri, Mar 13, 2009 at 6:58 PM, Wendy Smoak <wsmoak@gmail.com> wrote:
>> > I was wondering... what was the motivation for attaching Build Queues
>> > to a Schedule?
>> >
>> > It seems like it would have been simpler to have these as separate
>> > things. =A0There are schedules, builds happen, and there are some queu=
es
>> > to use. =A0What do we gain by connecting them that we wouldn't have
>> > otherwise?
>> >
>> > (I've invented a possible use for it, but I can't quite get all the
>> > way through the use case with the current implementation.)
>> >
>> > Thanks,
>> > --
>> > Wendy
>> >
>>
>