Hi Chris, > -----Original Message----- > From: Christopher Lenz [mailto:[EMAIL PROTECTED] > Sent: 07 November 2003 16:18 > To: Cactus Developers List > Subject: Re: cvs commit: jakarta-cactus build.properties.vmassol build- > common.xml build.xml > > Hi Vincent, > > just out of curiosity, will you be using CruiseControl to generate the > nightly builds, or something else?
Nope. For now it's simply a shell script that does a cvs checkout, run "ant release", does an scp of the generated release files and an "ant upload" for the documentation. What I'd like to do is to use DamageControl (http://damagecontrol.codehaus.org/builds/damagecontrol/docs/index.html, http://wiki.codehaus.org/general/DamageControl). It is currently set up on codehaus and I have the right to use it (thanks to Bob). The machine on codehaus is undergoing maintenance ATM so I'll wait till it's up again. > > BTW, why does the environment file need to be in CVS? Actually I knew you would be asking this question! The main reason is that DamageControl is parameter-less (only the build command line can be set. Not sure how long the command line can be) so everything has to be in the build itself. And I think it may be a good thing to control environment stuff. Thanks -Vincent > > Cheers, > -chris > > [EMAIL PROTECTED] wrote: > > vmassol 2003/11/07 06:10:42 > > > > Modified: . build-common.xml build.xml > > Added: . build.properties.vmassol > > Log: > > Added support for controlling properties for well-known environments. > The "vmassol" one is the one I'm setting up at home to generate nightly > builds of Cactus (to replace Gump which is not currently working) > [..] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
