Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 68897 invoked from network); 4 Jul 2007 15:40:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jul 2007 15:40:00 -0000 Received: (qmail 12626 invoked by uid 500); 4 Jul 2007 15:40:03 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 12595 invoked by uid 500); 4 Jul 2007 15:40:02 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 12582 invoked by uid 99); 4 Jul 2007 15:40:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 08:40:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [62.193.206.9] (HELO webmail9.amenworld.com) (62.193.206.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 04 Jul 2007 08:39:59 -0700 Received: (qmail 22478 invoked from network); 4 Jul 2007 15:39:44 -0000 Received: from 133.52.68-86.rev.gaoland.net (HELO ?127.0.0.1?) (86.68.52.133) by 0 with SMTP; 4 Jul 2007 15:39:44 -0000 Message-ID: <468BBF2D.5000702@venisse.net> Date: Wed, 04 Jul 2007 17:39:25 +0200 From: Emmanuel Venisse User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: "continuum-dev@maven.apache.org" Subject: CONTINUUM-1226 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I looked today at CONTINUUM-1226 and I confirm it doesn't work and it won't work without a DB schema change. To fix it, we must attach the build definition to the build result and remove the build result from the build definition (lastBuildId) that is totally wrong since a build definition can be a group build definition. With the build definition attached to the build result, we'll can find all scm changes since latest execution of the current build definition on the current project and multiple build definitions on a project will work. I think this DB schema change must be done before the release of 1.1-beta-1, so the migration between betas will be easier Emmanuel