Correct an issue that occurs when you delete a job specifically tied to

a slave node

(See email to users@ titled: "Deleting jobs on slaves doesn't delete job
workspace")

Basically this properly removes the workspace directory of jobs assigned
to slave machines when the job owning the workspace is removed.

There still exists an issue where renaming a job assigned to a slave
machine copies the workspace to a new workspace folder named after the
new job, but fails to properly remove the former workspace directory
(patch is being developed now, expected tomorrow)
Developed-by: NAdam Christian <adam@slide.com>
Acked-by: NR. Tyler Ballance <tyler@slide.com>



git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@14707 71c3de6d-444a-0410-be80-ed276b4c234a

core/src/main/java/hudson/model/AbstractProject.java

@@ -178,6 +178,11 @@ public abstract class AbstractProject<P extends AbstractProject<P,R>,R extends A
         FilePath ws = getWorkspace();
         if(ws!=null)
             getScm().processWorkspaceBeforeDeletion(this, ws,getLastBuiltOn());
+        try {
+            ws.deleteRecursive();
+        } catch (InterruptedException e) {
+            // Ignoring for now
+        }
         super.performDelete();
     }