Hi, With previous version of CruiseControl.NET (eg: 1.4.0.3524), the current directory was not changed when the server was started. This made it easy to keep configuration file ccnet.config, state files, artifacts and working directories outside of the directory tree where CruiseControl.NET was installed. However, with 1.5 RC1, it seems that the server is able to load the configuration file ccnet.config from the current directory but later changes the current directory to the location of the server binary. And this is where it now saves the state files, artifacts and working directories. I saw CCNET-1565 that also identified this problem as a breaking change. But it was closed. I also saw CCNET-144 and other similar issues, but they are all considered minor, and won't probably be fixed until 1.6.
I understand that the root cause of this problem could be difficult to find, as the changes in the current directory may have been done almost anywhere in the CruiseControl.NET source code. But I think it should be address before 1.6, since it is a breaking change from previous release. Even the documentation would need to be updated, and the artifacts and working directories are said to be "Relative paths are relative to a directory called the project Name in the directory where the CruiseControl.NET server was launched from." Could this problem be addressed in some way, before 1.6? For example, could the state files, artifacts and working directory be relative to the location of the configuration file ccnet.config. This would give everybody an easy way to keep their files outside of CruiseControl.NET installation directory tree. Thanks, Georges To unsubscribe from this group, send email to ccnet-user+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
