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 ken.liu@gmail.com designates
 209.85.198.244 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=QF4Apqs0ypPxtVp7BK0Q1VqxBG8pIOQe6arFpXEqmwq4XfdlwrCelks2Vlop9kFCEi
         htSv228nVHo5gq4RAKXMw9b86V4UBtoH0g+aZh58x8fygMpGLR3YPp2SDZ0spbllnXTi
         PUy+2lc6k1Z/KC08EBIrYqy9d7Sem84Dfte8g=
Message-ID: <748e286f0809120728yd1729dal21a129d12033e28a@mail.gmail.com>
Date: Fri, 12 Sep 2008 10:28:42 -0400
From: "Ken Liu" <ken.liu@gmail.com>
To: dev@continuum.apache.org
Subject: Re: Are templated build definitions shared among groups?
In-Reply-To: <adba96190809111529m5096acedjeb98685beb33d169@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_29497_12191120.1221229723023"
References: <adba96190809031937y6c38f43dqfee410035a48555f@mail.gmail.com>
	 <adba96190809111529m5096acedjeb98685beb33d169@mail.gmail.com>

------=_Part_29497_12191120.1221229723023
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Wendy -

I think these things you mentioned are a symptom of a greater problem - the
concept of "build definitions" is sort of unclear from the user interface
perspective. When using 1.1 for the first time, I was pretty surprised by
the way that build definitions are shared.

Perhaps this is due to a lack of documentation, but somehow the UI needs to
better communicate which build definitions are shared and how they are
shared.

Ken

On Thu, Sep 11, 2008 at 6:29 PM, Wendy Smoak <wsmoak@gmail.com> wrote:

> On Wed, Sep 3, 2008 at 7:37 PM, Wendy Smoak <wsmoak@gmail.com> wrote:
>
> > This is still on my list to test and verify, but I suspect that when a
> > build definition is added to a project group at group creation time
> > (i.e., from a template) then that build definition is shared between
> > all groups created this way.
> >
> > When I look at the Build Definition Templates page, I see only one
> > build definition.
> >
> > However, if I add build definitions to existing project groups, then I
> > see new build definitions show up on the templates page.
>
> Working with build definitions, I've observed
>
> 1. Each time you add a project group, a copy of each templated build
> def is created.  (So they are NOT shared.)
>
> 2. Each time a project group makes a change to their build definition,
> a new build def is added to the list. (Is this correct?)
>
> 3. The list of build definitions on the Build Definitions Templates
> page can get quite long, and it's not clear which build definitions
> are actually in use.
>
> 4. The 'delete' icon is disabled for copies of the default build
> definitions, even if the build def is edited so that a new one appears
> and no one is actually using the 'original'.
>
> 5. The delete icon is enabled on user-added build defs and copies,
> even if the build def is in use and trying to delete it will cause a
> constraint violation complete with error message and stack trace.
>
> I'll open some issues...
>
> --
> Wendy
>

------=_Part_29497_12191120.1221229723023--