Continuous Integration and test environment availability

When a developper does not have an environment to run the unit tests of a projet, never allows this team member to check in, even if you have a continuous integration server running.

If the build is broken, this programmer will have to perform several check in with the new code and wait for the next build in order to know if the build was fixed. Et voilà, the continuous integration server has become the test environment for this person...

Simple CruiseControl + Ant example

I always have a hard time finding online a simple example of CruiseControl + Ant file whenever I need to quickly setup a Continuous Integration server for a project. So here is the configuration I had set up for the open source project TSP (Transport Sample Protocol) :

<br /><cruisecontrol><br /> <project name="tsp" buildafterfailed="false"><br /><br /> <listeners><br /> <currentbuildstatuslistener file="logs/${project.name}/status.txt"><br /> </listeners><br /><br /> <bootstrappers><br /> <cvsbootstrapper localworkingcopy="projects/${project.name}/make" file="cc-build.xml"><br /> </bootstrappers><br /><br /> <modificationset quietperiod="30"><br /> <cvs localworkingcopy="projects/${project.name}"><br /> </modificationset><br /><br /> <schedule interval="300"><br /> <ant anthome="apache-ant-1.6.5" buildfile="projects/${project.name}/make/cc-build.xml"><br /> </schedule><br /><br /> <log><br /> <merge dir="projects/${project.name}/target/test-results"><br /> </log><br /><br /> <publishers><br /> <htmlemail mailhost="smtp.blablablablabla.fr" reportsuccess="fixes" returnaddress="foo@blablablablabla.fr" subjectprefix="[CruiseControl]" skipusers="true" spamwhilebroken="true" xsldir="webapps/cruisecontrol/xsl" css="webapps/cruisecontrol/css/cruisecontrol.css"><br /> <always address="foo@blablablablabla.fr"><br /> <always address="bar@blablablablabla.fr"><br /> </htmlemail><br /> </publishers><br /> <br /> </project><br /></cruisecontrol><br /><br /><br />
For TSP the Ant build file was there to trigger the C build :
<br /><project name="tsp" default="build" basedir=".."><br /><br /> <property name="build.dir" value="tsp_cc_build"><br /> <property name="tsp.dir" value=".."><br /><br /> <macrodef name="cmake"><br /> <attribute name="flags" default=""><br /> <sequential><br /> <exec dir="${build.dir}" executable="cmake" failonerror="true"><br /> <arg line="@{flags} ${tsp.dir}"><br /> </exec><br /> </sequential><br /> </macrodef><br /><br /> <macrodef name="make"> <br /> <sequential><br /> <exec dir="${build.dir}" executable="make" failonerror="true"><br /> </sequential><br /> </macrodef> <br /><br /> <macrodef name="cvs-update"><br /> <attribute name="workDir"><br /> <sequential><br /> <exec dir="@{workDir}" executable="cvs" failonerror="true"><br /> <arg line="update -dP "><br /> </exec><br /> </sequential><br /> </macrodef><br /><br /> <target name="build" depends="update"><br /> <antcall target="vanilla"><br /> <antcall target="xmlrpc"><br /> </target><br /><br /> <target name="vanilla" depends="clean"><br /> <cmake/><br /> <make/><br /> </target><br /><br /> <target name="xmlrpc" depends="clean"><br /> <cmake flags="-DBUILD_XMLRPC=ON"><br /> <make/><br /> </target><br /><br /> <target name="clean"><br /> <delete dir="${build.dir}"><br /> <mkdir dir="${build.dir}"><br /> </target><br /><br /> <target name="update"><br /> <cvs-update workdir="${basedir}"><br /> </target><br /><br /></project><br /><br />
For TSP the setup instruction were :

• install a binary distribution of cruise control
• replace the config.xml file with the previous file. Change the email addresses of the 'returnaddress', and the 'always address'. You can add as many 'always address' as you want
• go to the 'projects' directory of the cruisecontrol install and perform an anonymous check out of tsp :

<br />cd projects<br />cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/tsp co tsp<br />
you can test the build without cruise control if Ant is available :
go to projects/tsp/make and launch :
<br />ant -f cc-build.xml<br />
If everything is OK, with the build, run the cruisecontrol.sh script. you're done,
cruisecontrol is up and running.