Create a Class Library project to build the assembly that will contain your custom builder plug-in. The assembly that it produces should be named: 'ccnet.*.plugin.dll' (where the star represents the name you choose).
Add your new custom builder class.
The class must implement the ThoughtWorks.CruiseControl.Core.ITask interface (found in the ThoughtWorks.CruiseControl.Core.dll assembly).
Mark your class with the NetReflectorReflectorType attribute. The name argument supplied to the attribute is the name of the element/attribute that will appear in the configuration file.
Add any configuration properties that you need, marking them with the NetReflectorReflectorProperty attributes accordingly. Note that the attribute names are case sensitive and must match exactly in the configuration.
Implement the Run method. The supplied IIntegrationResult should provide you with everything that you need to know about the current build.
Compile the assembly.
Copy the assembly into the folder containing the CruiseControl.NET assemblies (or the current directory that you are running the ccnet server from).
Modify your ccnet.config file in accordance with the sample config file below.
Sample Builder Class
using System;
using Exortech.NetReflector;
using ThoughtWorks.CruiseControl.Core;
namespace ThoughtWorks.CruiseControl.Sample.Builder
{
[ReflectorType("mybuilder")]
public class NAntBuilder : ITask
{
public void Run(IIntegrationResult result)
{
Console.WriteLine("Hello World!");
}
}
}
Sample Config File
<cruisecontrol>
<project name="myproject">
<tasks>
<mybuilder>
<!-- include custom builder properties here -->
</mybuilder>
</tasks>
</project>
</cruisecontrol>
For a more detailed explanation visit this blogsection Customizing Code
Just a slight gotcha: the custom plugin part of the dll name, the ReflectorType name, and the name used in the config file must all match exactly otherwise you'll see XML config errors like:
"Configuration document is likely missing Xml nodes required for properly populating CruiseControl"
In others words, if your custom plugin is called "myproject" then the corresponding entities have to be:
Just a slight gotcha: the custom plugin part of the dll name, the ReflectorType name, and the name used in the config file must all match exactly otherwise you'll see XML config errors like:
"Configuration document is likely missing Xml nodes required for properly populating CruiseControl"
In others words, if your custom plugin is called "myproject" then the corresponding entities have to be:
1.) DLL name: ccnet.myproject.plugin.dll
2.) code markup: [ReflectorType ("myproject")]
3.) config file:
<project>
<tasks>
<myproject>
...
</myproject>
</tasks>
</project>