From: Norman R. <no...@ra...> - 2006-10-04 00:38:20
|
Here's the reasoning behind my request: We have a VSS build server using cc.net, but because vss is sooo slow, we're set up some shadow folders on the build server (shadow folders automagically get a copy of everything checked in source control). The cc.net source control blocks are then set up as follows: - Filtered Source : exclude = C:\ - Multi Source : requireChangesFromAll = true - FileSystem : root = shadow folders - VSS : project = $/project/location That way VSS isn't required to do (slow) history checks every time it needs to determine if any changes have been made. The filter also removes file changes from the change list so that only VSS changes are listed. It does mean that cc.net gets in a 'loop' if file changes occur, without any VSS changes :-( Proprosed solution: fix VSS to not use any bandwidth *ahem* Real proposed solution: - Filtered Source : exclude = C:\dev\project - Multi Source : requireChangesFromAll = true - FileSystem Source : root = C:\dev\project (i.e. the shadow folder) - Multi Source : *useFirstChangesOnly = true* - VSS Source : project = $/project/location - Null Source : *alwaysBuild = true* This way, if VSS changes are not detected, a set of 'fake' changes can be generated by the nullsource (add alwaysBuild parameter), and if VSS changes are detected, then the nullsource is not asked for a list of changes. Thoughts? -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |