Here's how I set CCNet up: http://badwords.org/w/Configure_CruiseControl.NET
(Note that this page is a work-in-progress.) On Dec 9, 11:51 pm, Mark <[EMAIL PROTECTED]> wrote: > I'm sure that I'm going crazy, but I rememeber recently reading a web > site that talked about best practices for setting up a appropriate > directory structure for the ccnet server, the working folders, > artifact directories etc. IIRC, it also didn't really install ccnet > using the windows installer, but rather the server and webdashboard > files were put together in a different manner from the installed > files. > > For the life of me, I can't find the site anymore. So, I'm looking > for suggestions on what others think as an apporpriate structure for > the ccnet file and working/artifact folders for ccnet projects. Does > anyone else change the file structure of the ccnet files themselves > (i.e. put the server in a different location from where it is normally > installed at)? > > Ultimately, I'd like to be able to store my ccnet file in source > control so that in a recovery situation, it would be trivial for me to > get the files from perforce onto a new machine and with very few steps > get my server back up and running again. This situation would also > make deployment of new ccnet servers within the organization easier. > Individual projects could set up their own ccnet.config (under some > unique name) check those config files into source control and then > basically with a single sync, they could mimic our "standard" ccnet, > including our modified and unique xsl files and with a quick change to > the ccservice.exe.config file to point to the project specific config > file, they are up and running. > > I'm curious what thoughts others might have. Thanks in advance.
