Continuous Integration

Christopher Wright dhasenan at gmail.com
Wed Mar 26 05:17:46 PDT 2008


Christopher Wright wrote:
> Jason House wrote:
>> Does anyone have a setup for doing continuous integration with d?
> 
> I'm going to start on that now, since DUnit (latest svn) can output 
> vaguely junit-compatible xml. It'll be using CruiseControl. By tomorrow, 
> I'll be able to tell you when you should start bothering me about it in 
> earnest.

Okay, assuming you are using dsss, you can simply use:

<schedule interval="60">
     <exec workingdir="projects/${project.name}" 
command="/usr/local/bin/dsss" args="build" timeout="5000" />
</schedule>

If you have a binary that includes your tests, you can change that to:

<schedule interval="60">
     <composite>
         <exec workingdir="projects/${project.name}" 
command="/usr/local/bin/dsss" args="build" timeout="5000" />
         <exec workingdir="projects/${project.name}" command="./binary" 
args="some-args" />
     </composite>
</schedule>

If you don't use <composite>, well, that's entirely allowed, but only 
the first element will be executed.

I don't have xml output for dunit working correctly with cruisecontrol yet.



More information about the Digitalmars-d mailing list