-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins 1.430 & Red Hat Enterprise Linux Server release 5.5 (Tikanga)
When a project is deleted, its directory JENKINS_HOME/jobs/<project> is wiped out. Workspace directories are not deleted if they have been defined outside the project directory (in global system configuration), which has been the default for a while. In multi-node environment, there can be several leftover workspaces (on all slaves where the project has been built).
There is an easy workaround for this. One can manually delete unwanted leftovers. It would be nice if Jenkins could do proper cleaning, or offer workspace deletion when a project is about to be deleted.
- duplicates
-
JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace
-
- Resolved
-
- is duplicated by
-
JENKINS-34781 Cleanup node workspaces on orphan removal
-
- Closed
-
[JENKINS-11046] Project deletion does not wipe out project workspaces
Summary | Original: Project deletion does not wipe out custom workspace and custom build record directories | New: Project deletion does not wipe out project workspaces |
Description |
Original:
When a project is deleted, its directory JENKINS_HOME/jobs/<project> is wiped out. Workspace and build record directories are not deleted if they have been defined outside the project directory (in global system configuration). In multi-node environment, there can be several leftover workspaces (on all slaves where the project has been built). There is an easy workaround for this. One can manually delete unwanted leftovers. It would be nice if Jenkins could do proper cleaning, or offer workspace and build record deletion when a project is about to be deleted. |
New:
When a project is deleted, its directory JENKINS_HOME/jobs/<project> is wiped out. Workspace directories are not deleted if they have been defined outside the project directory (in global system configuration), which has been the default for a while. In multi-node environment, there can be several leftover workspaces (on all slaves where the project has been built). There is an easy workaround for this. One can manually delete unwanted leftovers. It would be nice if Jenkins could do proper cleaning, or offer workspace deletion when a project is about to be deleted. |
Workflow | Original: JNJira [ 141256 ] | New: JNJira + In-Review [ 175444 ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |