We do it this way: http://badwords.org/w/Configure_CruiseControl.NET#Bootstrap_Project We only have about a dozen low-traffic builds, though, so I haven't had problems with updates being missed.
Basically, I watch for changes to our .config and do a "build" on them, then copy over to the real config location. On Mar 5, 5:02 pm, badfrog <[email protected]> wrote: > Hi all, > > I'm having multiple problems using the "official" example "Configure > CruiseControl.Net to Automatically Update its Config File" over > athttp://confluence.public.thoughtworks.org/display/CCNET/Configure+Cru... > with TFS 2005. > > Specifically I have two major problems: First, updates to the file > seem to get sporadically missed, and attempts to force the update down > don't always correct the problem (might be related to a difference in > time zone between my TFS server and my cc.net server). Second, changes > to the project configurations contained in the file do not always > actually update the project configuration shown on the dashboard, nor, > based on subsequent build results, do they actually update the active > project configuration. I apparently have to remove the read-only flag > and hand update the file before the changes will show up (although the > log files seem to indicate the service detected the original > "automatic" change). > > The "official" setup just doesn't appear to work reliably enough in my > environment for me to actually use it, I don't want to be constantly > remoting into my cc.net server to hand-edit that config file. So, my > question to the group is, does anyone have a good, working alternate > solution for updating ccnet.config from source control?
