Question

We’ve decided to implement CC.NET to have a readily available build for our various projects in Subversion, but the challenge we’re facing is that we use some heavy references like NHibernate.dll which is quite large, and might not be very efficient to check out all the time by CC .NET.

Can anyone provide advice that could assist us in setting up the correct environment? Also, how does CC .NET handle references of other projects in SVN?

Thanks a ton

Answer 1

but the challenge we’re facing is that we use some heavy references
like NHibernate.dll which is quite large, and might not be very
efficient to check out all the time by CC .NET.

Cruisecontrol.net is a queuing system. It also provides a toolbox for running items in the queue when it’s their turn. ccnet simply executes tasks and manages things like build logs, build artifacts and sending emails about the build. So basically you’d setup ccnet to check out your SVN project and then build it.

Can anyone provide advice that could assist us in setting up the
correct environment?

The environment should be similar to the environment used to build the code. ccnet comes as an easy to use installer. You will need to install Internet Information Services prior to installing ccnet.

Also, how does CC .NET handle references of other projects in SVN?

You mean SVN externals? ccnet has a thing called source controls. One of the source controls in ccnet is SVN and it provides a way to check for differences in the externals of a repository or to avoid the externals when checking for differences. SVN Source Controls in ccnet