I'm using the latest CC 2.1.3 for automated builds and nightlies. The
maven integration works just fine. I had no problems even recongizing
build failures. You can update your project with the CC bootstrappers as
well. The following code shows how I did it.
...
<bootstrappers>
<currentbuildstatusbootstrapper
file="<path_to_project_log_dir>/currentbuildstatus.txt"/>
<cvsbootstrapper
localWorkingCopy="<path_to_local_working_copy>/projectA"
cvsroot=":pserver:[EMAIL PROTECTED]:/home/cvs" />
</bootstrappers>
<modificationset quietperiod="300">
<cvs cvsroot=":pserver:[EMAIL PROTECTED]:/home/cvs"
localworkingcopy="<path_to_local_working_copy>/projectA"/>
</modificationset>
<schedule interval="3600">
<maven mavenscript="<path_to_maven>/bin/maven"
projectfile="<path_to_local_working_copy>/projectA/project.xml"
goal="clean checkstyle:report test site:deploy"
multiple="1"/>
</schedule>
...
Cheers,
Dominik
On Thu, 2003-08-14 at 23:24, Brett Porter wrote:
> Did you try the most recent version of CC? I'm using 2.1.3 with the
> following:
> <maven mavenscript="/usr/local/maven/bin/maven"
> goal="scm:update-project|clean test|site:deploy"
> projectfile="checkout/common/BTcore/project.xml"/>
>
> As long as projectfile is already checked out, this should work, although
> you'll need to download the SCM plugin from JIRA. Or write the goal itself -
> its just a wrapper for the ant task in this case.
>
> Works like a charm! Busted a developer committing without running the unit
> tests just yesterday :)
>
> Cheers,
> Brett
>
>
> > -----Original Message-----
> > From: Simon Matic Langford [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 14 August 2003 6:53 PM
> > To: 'Maven Users List'
> > Subject: RE: Maven Return Codes in a Continuous Integration
> > environment
> >
> >
> > I use cruisecontrol and we couldn't get the maven integration
> > working, so we just use a wrapper ant script with an <exec
> > failonerror="true"> and we definitely see non zero error
> > codes, ususally 70.
> >
> > The information contained in this e-mail is intended only for
> > the person or entity to which it is addressed and may contain
> > confidential and/or privileged material. If You are not the
> > intended recipient of this e-mail, the use of this
> > information or any disclosure, copying or distribution is
> > Prohibited and may be unlawful. If you received this in
> > error, please contact the sender and delete the material from
> > any computer. The views expressed in this e-mail may not
> > necessarily be the views of The PCMS Group plc and should not
> > be taken as authority to carry out any instruction contained.
> >
> >
> > > -----Original Message-----
> > > From: Tomasz Pik [mailto:[EMAIL PROTECTED]
> > > Sent: 14 August 2003 09:47
> > > To: Maven Users List
> > > Subject: Re: Maven Return Codes in a Continuous Integration
> > > environment
> > >
> > >
> > > [EMAIL PROTECTED] wrote:
> > > > There are these in App.java
> > > >
> > > > /** return code for ok processing */
> > > > private static final int RC_OK = 0;
> > >
> > > <cut/>
> > > Maybe make them public and document their values as a part
> > > of javadoc. So:
> > >
> > > /**
> > > * <b><code>0</code></b< return code for ok processing.
> > > */
> > > public static final int RC_OK = 0;
> > >
> > > ?
> > >
> > > Regards,
> > > Tomek
> > >
> > > >
> > > > dIon Gillard, Multitask Consulting
> > >
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > 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]
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
