Sometimes developers and release engineers can't come up with a good way to ensure that all files modified by the build are under a common root within the workspace. But modern SCM systems give us the capability to report on the status of files within a given working copy. Improving the integration with SCM systems to restore the Destination path specified in a Repository object to its pristine state would give us extra piece of mind that our build workspace is fresh and clean when we want it to be. Sometimes a build may fail catastrophically before the step the runs our cleanup target. I don't want to delete the whole workspace because then it's a full checkout for the next build.
I primarily use SVN so naturally I would like to see this level of integration in the Subversion plugin. But I imagine people using other tools would like the same.
Description
Sometimes developers and release engineers can't come up with a good way to ensure that all files modified by the build are under a common root within the workspace. But modern SCM systems give us the capability to report on the status of files within a given working copy. Improving the integration with SCM systems to restore the Destination path specified in a Repository object to its pristine state would give us extra piece of mind that our build workspace is fresh and clean when we want it to be. Sometimes a build may fail catastrophically before the step the runs our cleanup target. I don't want to delete the whole workspace because then it's a full checkout for the next build.
I primarily use SVN so naturally I would like to see this level of integration in the Subversion plugin. But I imagine people using other tools would like the same.