ok, so if i've got it right..... the plugin coordinates maven projects with cruisecontrol. Cruisecontrol config file is built using maven project descriptor info for cvs properties etc. then cruisecontrol executes calling maven goals.
I downloaded cruisecontrol, built cruisecontrol, executed the plugin to create the cruisecontrol config then executed cruisecontrol...........
error :( config at the bottom,
any ideas - sorry if this is getting a bit off-topic for a maven list.
[cc]Nov-28 15:11:23 Main - CruiseControl Version 2.1 Compiled on November 28 2003 1508
[cc]Nov-28 15:11:23 trolController- projectName = [op]
[cc]Nov-28 15:11:23 trolController- No previously serialized project found: D:\ri\op\op\op\op
[cc]Nov-28 15:11:23 Project - Project op: reading settings from config file [D:\ri\op\op\op\cruisecontrol.xml]
[cc]Nov-28 15:11:23 Main - Project descriptor D:\ri\op\op\op\checkout\op\project.xml does not exist
[cc]Nov-28 15:11:23 Main - Usage:
[cc]Nov-28 15:11:23 Main -
[cc]Nov-28 15:11:23 Main - Starts a continuous integration loop
[cc]Nov-28 15:11:23 Main -
[cc]Nov-28 15:11:23 Main - java CruiseControl [options]
[cc]Nov-28 15:11:23 Main - where options are:
[cc]Nov-28 15:11:23 Main -
[cc]Nov-28 15:11:23 Main - -port number where number is the port of the Controller web site
[cc]Nov-28 15:11:23 Main - -configfile file where file is the configuration file
<cruisecontrol>
<project name="op">
<bootstrappers>
<currentbuildstatusbootstrapper file="D:\ri\op\op\op/target/cc-logs/currentbuildstatus.txt">
</currentbuildstatusbootstrapper>
</bootstrappers>
<modificationset>
<cvs localWorkingCopy="D:\ri\op\op\op/checkout/op" cvsroot=":pserver:[EMAIL PROTECTED]:/OnePort/data/cvsroot">
</cvs>
</modificationset>
<schedule interval="300">
<maven goal="scm:update|clean test|site:deploy" projectfile="D:\ri\op\op\op/checkout/op/project.xml" mavenscript="D:\java\apache\maven/bin/maven">
</maven>
</schedule>
<publishers>
<currentbuildstatuspublisher file="D:\ri\op\op\op/target/cc-logs/currentbuildstatus.txt">
</currentbuildstatuspublisher>
<htmlemail logdir="D:\ri\op\op\op/target/cc-logs/op" mailhost="localhost" css="../cc/reporting/jsp/css/cruisecontrol.css" subjectprefix="[BUILD]" returnaddress="[EMAIL PROTECTED]" defaultsuffix="@oneport.com" xsldir="../cc/reporting/jsp/xsl">
<failure address="[EMAIL PROTECTED]">
</failure>
</htmlemail>
</publishers>
</project>
</cruisecontrol>
D:\ri\op\op\op>
[EMAIL PROTECTED] wrote:
Nathan Coast <[EMAIL PROTECTED]> wrote on 28/11/2003 03:05:20 PM:
Hi,
Is it 'expected' that cruisecontrol will be the defacto mechanism for
performing
CI within maven? In other words is it worth investing the time to learn
cruisecontrol?
I don't know if it's worth *your* time, but it was up and going quickly for me.
As a cruisecontrol newbie I'm not sure where the boundaries of
cruisecontrol and
maven overlap. What I'm looking for is some way of schedulling cvs
checkout,
build, deploy, test, email someone when it goes wrong.
It does that easily.
Is there a more recent maven plugin for cruisecontrol? I had a look at
the
current plugin and the run method doesn't seem to do much :)
Who needs the run method?
I used the plugin to generate the config file and run CC by batch file on our CI/testing box.
I had to tweak the CC plugin a bit as some of the property defaults make no sense.
-- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
--------------------------------------------------------------------- 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]
