[JIRA] [core] (JENKINS-25912) Workspaces remain on disk after job has been ( deleted, moved, renamed )

[jthe...@me.com (JIRA)]

Jan Henne created JENKINS-25912 Workspaces remain on disk after job has been ( deleted, moved, renamed ) Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Dec/14 1:01 PM Description: Scenario_1: Job foo runs once and creates a workspace named "foo". After renaming foo to foofoo the workspace "foo" still exists if it wasn't deleted manually. If foofoo runs now it creates it's own workspace. # ls foo foofoo The problem by having multiple jobs with huge workspaces is the disk space. In addition to that it's not nice to have some dead folders lying around on your file-system. Scenario_2: If job foo is executed in parallel it creates multiple workspaces. This is fine as long as you're not using the "Wipe Out Current Workspace" button. If so the only workspace that is getting deleted is foo but not the additional ones. Example before wiping the workspace: #ls foo foo@2 foo@3 foo@4 Example after wiping the workspace: #ls foo@2 foo@3 foo@4 Environment: 1.590 redhat 5 Java 7 Project: Jenkins Labels: security jenkins workspace Priority: Major Reporter: Jan Henne

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.