How can I tolerate an unavailable remote host referenced in a modificationset/filesystem specification?

I'm building a new CruiseControl project that contains something like the following:

<modificationset quietperiod="${default.quietperiod}">
        <filesystem folder="//crasimvs09vm31/c$/WINDOWS/system32/drivers/etc/hosts" username="WebSphere_admin" />
</modificationset>

In my environment, it is not uncommon for this remote host (crasimvs09vm31) to be unavailable (e.g. taken down for maintenance, patching, etc.) In testing (with CruiseControl Version 2.8.2 Compiled on January 12 2009 1535), if the host is unavailable then CruiseControl crashes with the following:

ERROR Main             - error setting config file on controller
net.sourceforge.cruisecontrol.CruiseControlException: folder \\crasimvs09vm31\c$\WINDOWS\system32\drivers\etc\hosts must exist for FileSystem
        at net.sourceforge.cruisecontrol.util.ValidationHelper.fail(ValidationHelper.java:90)
        at net.sourceforge.cruisecontrol.util.ValidationHelper.assertTrue(ValidationHelper.java:85)
        at net.sourceforge.cruisecontrol.sourcecontrols.FileSystem.validate(FileSystem.java:69)
        at net.sourceforge.cruisecontrol.ModificationSet.validate(ModificationSet.java:391)
        at net.sourceforge.cruisecontrol.ProjectConfig.validate(ProjectConfig.java:111)
        at net.sourceforge.cruisecontrol.CruiseControlConfig.handleProject(CruiseControlConfig.java:423)
        at net.sourceforge.cruisecontrol.CruiseControlConfig.parse(CruiseControlConfig.java:172)
        at net.sourceforge.cruisecontrol.CruiseControlConfig.<init>(CruiseControlConfig.java:133)
        at net.sourceforge.cruisecontrol.config.XMLConfigManager.loadConfig(XMLConfigManager.java:86)
        at net.sourceforge.cruisecontrol.config.XMLConfigManager.<init>(XMLConfigManager.java:78)
        at net.sourceforge.cruisecontrol.CruiseControlController.setConfigFile(CruiseControlController.java:93)
        at net.sourceforge.cruisecontrol.Main.createController(Main.java:159)
        at net.sourceforge.cruisecontrol.Main.start(Main.java:126)
        at net.sourceforge.cruisecontrol.launch.Launcher.run(Launcher.java:259)
        at net.sourceforge.cruisecontrol.launch.Launcher.main(Launcher.java:117)
2009-03-07 16:01:51,094 [main     ] FATAL Main             - folder \\crasimvs09vm31\c$\WINDOWS\system32\drivers\etc\hosts must exist for FileSystem

This seems to be a very common event for all CruiseControl users, but am embarrassed that I am unable to find a procedure for how to code my CruiseControl project to tolerate this. Even if we have our automation restart CruiseControl while the remote host remains unavailable, it will fail again on the same error so the net effect is that CruiseControl cannot do any work (either for this project or for any other project). Unless, of course, the project were removed from the configuration during the period of unavailability.

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user