Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 66045 invoked from network); 9 Feb 2009 18:23:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Feb 2009 18:23:17 -0000 Received: (qmail 3073 invoked by uid 500); 9 Feb 2009 18:23:15 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 3044 invoked by uid 500); 9 Feb 2009 18:23:15 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 3033 invoked by uid 99); 9 Feb 2009 18:23:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2009 10:23:15 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cs@schulte.it designates 217.69.77.126 as permitted sender) Received: from [217.69.77.126] (HELO smtp.rent-a-mailserver.de) (217.69.77.126) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2009 18:23:06 +0000 Received: from [192.168.10.198] (cable-82-119-20-85.cust.blue-cable.de [82.119.20.85]) (user=cs@schulte.it mech=CRAM-MD5 bits=0) by smtp.rent-a-mailserver.de (8.13.8/8.13.8/Debian-3) with ESMTP id n19IMdmx023029 for ; Mon, 9 Feb 2009 19:22:40 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=schulte.it; s=default; t=1234203760; bh=1lrl8njbg3B2TwfdIOJtn0EJht3cwvCZ1XhAD6hXDho=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=UDGLubeumx+B nsERRgE6/RvR0TcAPPJzzueG3U6Y9KewKp3PW3OUrslJzVPeJ2qTvynH0a1ec6H0Jzu SV7YMJpSkfRPtE9DzAjwn+ikTxrvGO2cKTipYoqiA+X2WBCbkt/if9fUoNHo9SbUxYe qL8uMQyRkBeDzHrkIQ8m2rEO8= Message-ID: <4990746D.2050902@schulte.it> Date: Mon, 09 Feb 2009 19:22:37 +0100 From: Christian Schulte User-Agent: IceDove 1.5.0.14eol (X11/20090105) MIME-Version: 1.0 To: users@continuum.apache.org Subject: Re: Group build definition not executed when there is a project build definition ? References: <49906C28.2090208@schulte.it> In-Reply-To: X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (smtp.rent-a-mailserver.de [217.69.77.126]); Mon, 09 Feb 2009 19:22:40 +0100 (CET) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on smtp.rent-a-mailserver.de X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on smtp.rent-a-mailserver.de X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-0.8 required=8.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.3 Wendy Smoak schrieb: > On Mon, Feb 9, 2009 at 10:47 AM, Christian Schulte wrote: > >> I added a multi-module project to continuum and have a build definition >> at group level like 'clean deploy'. I would like continuum to execute an >> additional build definition only for the parent project like 'clean >> site-deploy'. > ... >> How can I configure the build-definitions to be executed both ? > > What version of Continuum? There was an issue with the first build > "consuming" the changes, so that subsequent builds wouldn't execute. > Not sure when/if it was resolved, but it should be in JIRA. > > As a workaround, you could enable the 'Always Build' checkbox on that > build def to get the site published regularly. > This is with continuum-1.2.3. I just added the group build definition to the parent project to see if that makes continnum execute both definitions when both declared at project level. Have to wait until the next schedule now. Will try 'Always Build', if that does not work. Btw, continuum is backed by a postgres database here. Will the JDO implementation correctly migrate the database automatically when upgrading to 1.3 ? Something like downloading 1.3, setting up the database connection to point to the same database currently in use by 1.2.3 and let continuum 1.3 migrate the database automatically during startup ? -- Christian