Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
CentOS 5.5
JRE 1.6.0
Jenkins 1.413
Description
If a project is configured with a "blank" custom workspace in it's Advanced Project Options, then when the workspace is cleaned, $JENKINS_HOME is deleted.
More specifically, if the "Use custom workspace" option is ticked, but the "Directory" field is not filled in, then the workspace directory is effectively $JENKINS_HOME.
Presumably this is because (as the docs mention) the custom workspace is relative to $JENKINS_HOME.
This is a serious issue, because a workspace clean removes all Jenkins workspaces, all Jenkins job configuration etc. without warning.
Please protect silly people like me from myself!!!!!
Integrated in
jenkins_main_trunk #848
Possible fix for
JENKINS-9806, fix empty customWorkspace -if empry, replace it by null (i.e. no custom workspace)[FIXED JENKINS-9806] the actual fix are in the two previous commits.
Kohsuke Kawaguchi : 8b4f30a162e8169a0537ae25d406aa86c7609dd0
Files :
Kohsuke Kawaguchi : a1ed1b2278592d61619986a615d56dac3bdc5b76
Files :