I am trying to get CruiseControl.net to build a branched folder in vault.
the plan is to structure the source repository with our released code is on the trunk (so we can make minor bug fixes to it then release ) and a single branch for all the new features for the upcoming release (new branch after each release) in the same way described on eric sinks blog http://www.ericsink.com/scm/scm_branches.html Do you know if it is possible to get CruiseControl.net software to build the most recent branch so that we can test our new features before merging them in? Thanks
