Hi, I've taken a look at the xml-rpc client, but I am a bit confused. I can use the xml-rpc to write a java class to build the project, but how does it get scheduled? Would I still have to use cron to schedule the java class to run or does xml-rpc does that too?
Thanks, Alex On 7/6/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
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 <[EMAIL PROTECTED]> 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 <tag> 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 <[EMAIL PROTECTED]> 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 >> >
