Ironicly enough, just started going down this feasibilty path.  I'm trying to 
use CruiseControl to do the autobuilds, while using the maven-cruisecontrol 
plugin to generate the config file for CruiseControl. Then, use CruiseControl 
to run (not the maven plugin to run cruisecontrol - didn't seem right, but if 
there is a good reason too I'm listening).

Unfortunately, either in ignorance or by practice, I've had to modify the 
created config file just to get it to work, and even then a lot of things are 
still broken in my environment(distribution jars, creating the j-unit logs for 
future reporting, etc). Part of the problem is partly in that I'm trying to do 
this with an EXISTING multi-module maven project (J2EE app to be specific).

Quick-start, assuming your project.xml is complete,
*download cruisecontrol (example: to /cc or c:/cc)
*install cruise control (google for 'cruisecontrol getting started' for help)
*add something like this to your project.properties file:
#-------------------------------------------------------------------------
# Maven Cruise Control
#-------------------------------------------------------------------------
maven.cruisecontrol.home = /cc/cruisecontrol-2.2
maven.cruisecontrol.mail.subjectprefix = [Build]
maven.cruisecontrol.checkout.dir = /cc/work/checkout
maven.cruisecontrol.mail.host = smtp.domain.blah
maven.cruisecontrol.config = /cc/work/cruisecontrol.xml

Then run the maven goal from your project:
cruisecontrol:configure

This creates the cruisecontrol.xml file. Then, from your cruisecontrol 
location, checkout the 'initial' cvs checkout (I think that is lame, but hey).  
Then, run cruisecontrol and pray.

Hopefully someone has some better, more easily digested and quicker 
instructions (particularly for multi-project setup!).

-D


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 03, 2004 8:56 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: Anyone really doing continuous integration with Maven?
> 
> 
> Bryan,
> 
> >So, my question is: Is anyone doing continuous integration builds
> >using Maven and how?
> 
> yes we have a project doing continuous integration using 
> CruiseControl which invokes maven build and then the maven 
> site generation.  
> is that what you are looking for?.
> 
> Regards,
> Manoj
> 
> 
> -----Original Message-----
> From: Thompson, Bryan B. [mailto:[EMAIL PROTECTED]
> Sent: 03 December 2004 13:47
> To: '[EMAIL PROTECTED]'
> Cc: Bebee, Bradley R.; Personick, Michael R.
> Subject: Anyone really doing continuous integration with Maven?
> 
> 
> Hello,
> 
> I have about 15 projects and a master POM for all of them.  I 
> use maven
> to build the individual projects as well as the integrated web site.
> When Maven does this multiproject build, it uses the current 
> development
> branch for the project that it is building, but the current stated
> _dependencies_, not from the source, for each dependency.
> 
> That is, Maven is NOT doing continuous integration in a multiproject
> build.  For example, Maven does not build the dependencies from the
> most current source for the stated revision of that dependency.
> 
> So, my question is: Is anyone doing continuous integration builds
> using Maven and how?
> 
> Thanks,
> 
> -bryan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> Visit our website at http://www.ubs.com
> 
> This message contains confidential information and is intended only 
> for the individual named.  If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.  Please 
> notify the sender immediately by e-mail if you have received this 
> e-mail by mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free 
> as information could be intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain viruses.  The sender therefore 
> does not accept liability for any errors or omissions in the contents 
> of this message which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.  This 
> message is provided for informational purposes and should not be 
> construed as a solicitation or offer to buy or sell any securities or 
> related financial instruments.
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to