Hi Looks like your using SourceSafe. If so, it is best to set up a user specifically for CCNet, this will makes things easier.
It is not really needed, since CCNet will run on another computer, but you may get weird results if an error occurs. Also, if you plan to use CCNet to update stuff in source safe, with a separate CCNet user, it is easier to see these things. with kind regards Ruben Willems On Wed, Dec 10, 2008 at 11:27 AM, Nickname <[EMAIL PROTECTED]> wrote: > > I created a configuration which appeared to work. I set my working > directory in my config file to C:\Temp\TempCCNet1 which corresponded > to the working directory for a given project in source safe. If I make > changes and check them in, CruiseControl responds and the dlls's etc > get built/updated. If, however I change the working directory (in the > config file only) to say C:\Temp\TempCCNet2, CruiseControl responds by > copying the source files only over to this new directory (the dll's > etc in C:\Temp\TempCCNet1 still get updated as before). I get a > message in the log: Set C:\Temp\TempCCNet2 as the default folder for > the project $/_Dev/Source/... (Y/N) N. > > If I want to extend this so others including myself can use it I > presumably need to be able to build the results in an directory other > than where my Visual Studio login has it's working directory set? > Should the person that sets this type of system up have an additional/ > separate set of credentials for source safe - one for the autobuild > process and one for individual development? Any thing that could throw > some light on this would be appreciated. > > Thanks >
