-
Improvement
-
Resolution: Unresolved
-
Major
-
Platform: All, OS: All
I recently created a new job and I thought tied it to a particular slave. Later
I realized that I had in fact forgotten to tie it to that slave, and the first
few builds ran on master. I corrected this and now it is running on the slave as
desired.
However now the master has an old copy of the job's workspace too. Since the
workspace is ~1 Gb, I would like to clean it up. But I want to leave the
actively used workspace on the slave intact, since recreating it is much slower
than running an incremental build - needs to do a full SCM checkout and then do
some big downloads.
Unfortunately there seems to be no way through Hudson's GUI to delete the
workspace on a particular node (master, in my case). I presume "Wipe Out
Workspace" would delete all copies.
Not sure what the best GUI would be, but perhaps the .../wipeOutWorkspace page
which displays a confirmation button could have a list of checkboxes, all
initially checked, listing the nodes on which a copy of the workspace currently
resides (if there is >1 such node). You could uncheck some of them if you
wished. The node on which the last build ran should be highlighted.
- is duplicated by
-
JENKINS-17098 Wipe out workspace does not remove parallel workspaces correctly
- Resolved
- is related to
-
JENKINS-7217 Clean Workspace only cleans the most recent slave
- Resolved
-
JENKINS-9898 when an agent goes offline the workspace for a build defaults to an older available build on a different agent
- Open
-
JENKINS-26138 Support workspaces for Pipeline jobs
- In Review
-
JENKINS-6216 Better progress feedback during workspace deletion
- Open