-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Hudson 1.376
If the custom workspace option is chosen, and the custom workspace directory is chosen to be in the workspace directory, the WorkspaceCleanupThread (if enabled) will always delete this directory, believing it's not associated with any job.
To reproduce:
- Create a job with a platform-appropriate path to a custom workspace in the workspace directory, e.g. workspace\custom
- Run a build to populate the workspace.
- Invoke the WorkspaceCleanupThread.
- The workspace will be deleted. Fine logs will show something like:
Feb 23, 2011 5:20:55 PM hudson.model.WorkspaceCleanupThread FINE: Directory d:\dev\hudsonBuilds\workspace\custom is not owned by any project
Workaround is to not create custom workspaces in the workspace directory.
- is duplicated by
-
JENKINS-3841 WorkspaceCleanupThread deletes shared workspaces
-
- Resolved
-
- is related to
-
JENKINS-17813 Jobs should have built in option to never clean workspace
-
- Resolved
-
I am unable to understand "the workspace directory is chosen to be in the workspace directory".... Can you please elaborate on this...
Also correct me if am wrong are there 2 kinds of workspaces
1) Workspace under remote FS root
2) Workspace under a job
If thats true does the issue apply to both. I am seeing this problem in both cases. So please give an example of wghat the custom workspace should be like. Will it be alrite to just have a Custom WS not under the slave root (hudson Root) workspace or the JOb workspace? Please let me know..
-Nitin