Cruise Control and CVS

Can anyone describe how <CVS/> and <CVSBoostrapper/> work in conjuction with
cvs calls from my ant script? I am thoroughly confused how CC tells if there
were modifications made since the last build.

I am seeing the changes, but only after I restart CC. Doing a cvs -n always
shows the changes, and I can typically see the ant output in the CC log that
the files got updated.

Here's a snippet of the xml file for CC:

<bootstrappers>
	<cvsbootstrapper cvsroot=":local:/cvs"
localWorkingCopy="/opt/TEMP/cruisecontrol-bin-2.8.2/projects/integration/temp"/> 

	<cvsbootstrapper cvsroot=":local:/cvs"
localWorkingCopy="/opt/TEMP/cruisecontrol-bin-2.8.2/projects/integration/appname"/> 
</bootstrappers>

<modificationset quietperiod="30">
	<cvs
localWorkingCopy="/opt/TEMP/cruisecontrol-bin-2.8.2/projects/integration/temp"
/>
	<cvs
localWorkingCopy="/opt/TEMP/cruisecontrol-bin-2.8.2/projects/integration/appname"
/>
</modificationset>

<schedule interval="30">
	<ant anthome="apache-ant-1.7.0"
buildfile="/opt/TEMP/cruisecontrol-bin-2.8.2/projects/integration/temp/build.xml"


-- 
View this message in context: http://old.nabble.com/Cruise-Control-and-CVS-tp30936657p30936657.html
Sent from the CruiseControl - User mailing list archive at Nabble.com.


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb