Awhile back when I was implementing a particular build into the CI model, I ran into a dependency debate; both with my own as well as the development group.  The project (A) in question has a lib dependency on another project (B).   The difference in view came when I suggested for A to depend [...]

CruiseControl.NET allows you to trigger a build base on another build’s successful completion. This is useful in that it allows builds with dependencies to be fully automated. When one is built successfully, another or more will be triggered. Here is an example code snippet: Within the <triggers> block, you can add an additional trigger similar [...]

Did you know that you can disable the “force” and “stop” build buttons for each project on CruiseControl.NET’s webdashboard? Inside the <remote services> code block, you can simply add allowForceBuild and allowStartStopBuild options: <remoteservices> <servers> <server name="BUILDSERVER01" url="tcp://buildserver01:21234 /CruiseManager.rem" allowForceBuild="false" allowStartStopBuild="false" /> </servers> </remoteservices> By doing this, you would be able to have better control [...]

To promote the spirit of Agile Development and Continuous Integration, groups of builds must be classified and treated differently within the development organization. These builds are as follows: Engineering: These builds lives on the individual developer’s machine. It should never see the light of day beyond this scope. This is merely a convenient build tool [...]