From continuum-users-return-2139-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Thu Jul 06 17:52:16 2006 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 78289 invoked from network); 6 Jul 2006 17:52:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jul 2006 17:52:15 -0000 Received: (qmail 33291 invoked by uid 500); 6 Jul 2006 17:52:15 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 32995 invoked by uid 500); 6 Jul 2006 17:52:14 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 32977 invoked by uid 99); 6 Jul 2006 17:52:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jul 2006 10:52:14 -0700 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.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; Thu, 06 Jul 2006 10:52:13 -0700 Received: (qmail 9841 invoked from network); 6 Jul 2006 17:51:52 -0000 Received: from 76.22.99-84.rev.gaoland.net (HELO ?127.0.0.1?) (84.99.22.76) by 0 with SMTP; 6 Jul 2006 17:51:52 -0000 Message-ID: <44AD4DAE.4050707@venisse.net> Date: Thu, 06 Jul 2006 19:51:42 +0200 From: Emmanuel Venisse User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: Projects in Continuum not building References: <20060706085347.97691.qmail@web26202.mail.ukl.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N You can do it with a xml-rpc client: http://maven.apache.org/continuum/guides/mini/guide-xmlrpc-api.html Emmanuel Alex Lam a écrit : > Hi, > > Thanks for the help. I think I found out the problem. My archive script was > placed in a project that had no changes. But the script is suppose to back > up my whole repository which has many projects. (Thus, the changes I > referred to were in my other projects.) After moving the script to the root > directory of all the projects, it seems to work, but I do not like this > solution. I believe I read somewhere that in future releases, Continuum > will allow scheduled force builds? In the meantime, one work around I have > in mind is to write a script that will hit the "Build Now" button on > Continuum and use cron to run it every night. Or is there a better way > to do > this? > > Thanks, > Alex > > On 7/6/06, Marcel Schutte wrote: >> >> Hi Alex, >> >> Try checking the continuum configuration of your project. Does it >> contain a value in the 'scm branch/tag' field? >> >> What happened with some of my continuum builds recently was that they >> must have started at a moment I was manually building a release. During >> a release, maven will commit two new versions of your pom. The first >> one contains a in the scm section. >> I think that continuum did the update at the moment this pom was the >> head revision and subsequently updated its configuration to use this >> tag. >> After this, it will never find changes again and therefore not run >> again. >> >> Your problem might be completely different, but it is worth checking >> this. >> >> Marcel >> --- Alex Lam wrote: >> >> > Hi all, >> > >> > I have a question on how Continuum works. >> > >> > I set up a script to check things out of SVN and burn it to a CD >> > every >> > night. >> > >> > However, Continuum doesn't seem to be executing the script on a >> > nightly >> > basis. >> > >> > The script did seem to work on Jun 29, when the revision number was >> > at 245. >> > This was the last time the script executed. >> > >> > However, for the past week, Continuum is not executing the script and >> > in the >> > logfile, it says "The project was not build because there are no >> > changes". >> > >> > The log file also states the revision number is at 249. Since Jun 29, >> > I have >> > been checking things in and out of my repository so I know there have >> > been >> > changes made to it. >> > >> > My question is " Is this an error in Continuum?" and how does >> > Continuum >> > detect that a build has no changes? Is it by the revision number? >> > >> > Thanks in advance for any help you can give me. >> > >> > -Alex >> > >> >> >> __________________________________________________ >> Do You Yahoo!? >> Tired of spam? Yahoo! Mail has the best spam protection around >> http://mail.yahoo.com >> >