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
 209.85.217.16 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:content-transfer-encoding:content-disposition
         :references;
        b=o2EuoKuxotZr9LrZLzXKcWOD7rTVXO05HJ7ioNmUmFFF6D+XTFbx/I0LN/XDKKF59i
         X0Wce5YCxbVh+CLWpo00n6D7tohWDjtRocMTkDrwpM501XUfUurxk467He/ygo22EG3E
         EP6ppcsIGHFDgQEroYAFUAelkbpL3QhsysIe4=
Message-ID: <adba96190809111529m5096acedjeb98685beb33d169@mail.gmail.com>
Date: Thu, 11 Sep 2008 15:29:44 -0700
From: "Wendy Smoak" <wsmoak@gmail.com>
To: dev@continuum.apache.org
Subject: Re: Are templated build definitions shared among groups?
In-Reply-To: <adba96190809031937y6c38f43dqfee410035a48555f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <adba96190809031937y6c38f43dqfee410035a48555f@mail.gmail.com>

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