CruiseControl.NET
Plug-ins, xls reports, configuration and more regarding CCNet.
A Little delayed compared to my hopes, but I finally got the next version up.
Again, this is manually packaged.
Source
Binaries
The configuration remains mostly the same, a "buildCondition" has been added, this controls if the build fails or not on missing parts, however the logic for this is not yet implemented.
Node
Description
...
As promised I have packaged a "release" of the Sandcastle Help File Builder plug-in.
This is manually packaged (since I don't yet have my build server making these packages automatically), so please bare with me on structure and what might be off or missing (well it should all be there, so missing is harsh said).
Source
Binaries
The configuration is very simple, in fact in some cases you can use it with only defining one parameter. Here is an example that defines a time-out, a project file and a publish path.
<sandcastle>
<projectFile>G:\Workspace\Help.shfb</projectFile>
...
So i have decided to start writing a Sandcastle Plug-in for CruiseControl.NET.
Currently we are using the folowing block at work to build and publish help files
(thanks to: http://blog.maartenballiauw.be/post/2007/08/28/automatically-generate-sandcastle-documentation-using-cruisecontrol-net-or-vsts-team-build.aspx)
1: <exec>
2: <executable>C:\Program Files\EWSoftware\Sandcastle Help File Builder\SandcastleBuilderConsole.exe</executable>
3: <baseDirectory><base directory></baseDirectory>
4: <buildArgs><project file></buildArgs>
5: <buildTimeoutSeconds>10800</buildTimeoutSeconds>
6: </exec>
7:
8: <exec>
9: <executable>xcopy</executable>
10: <buildArgs>"base directory\Help" "C:\Inetpub\wwwroot\api" /E /Q...