jason - 06/May/08 12:52 PM Done in change 4411, merged to trunk in change 4412.

James French - 06/May/08 02:32 PM That was quick! BTW will this allow checkouts to persist in the recipes folder as well as the work folder? Potential for massive savings there as it can take forever to check these sdks out from a busy svn server. Thanks again.

jason - 06/May/08 02:52 PM Hi James, This change will only affect builds using the update checkout schemes. It allows you to change the path used for persistent workspaces rather than it always being fixed. The default path is now: ${data}/work/${project}/${specification} which will resolve to the same value as used in earlier Pulse versions. You can set the system property pulse.persistent.work.dir to change this to something like: ${data}/work/${project}-${specification} to ensure only one level of nesting. You could even move these directories out of the data directory by replacing ${data}. It is important that the directory is writable by Pulse and is unique for each build specification. The recipes/ directory is a temporary workspace for builds that use a clean checkout scheme, thus those working copies are never persisted. So if you need persistent workspaces, you must use an update checkout scheme. If the checkout speed from SVN is a problem, then the "clean update" scheme may help - in this case the load on SVN is less, although there will be a large disk copy as the last step of bootstrap as the persistent workspace is copied to a new recipe directory for the build.

James French - 06/May/08 03:53 PM Brilliant! I realised (in a doh! moment) after I posted my last comment that clean checkouts should be just that, including the sdks so your change is perfect. Cheers Jason!