Due to the nature of the plugin, it seems natural for the clone-workspace-scm plugin to purge the workspace prior to cloning the parent. If this does not occur, files may be left dangling in the child workspace that are not part of the parent if that file was removed in a new build.