Jenkins.workspaceDir is supposed to default to $JENKINS_HOME/workspace/ on new installations: the "modern" location, consistent with that of slaves. But if you do not save the Jenkins global configuration during the first startup, on the next startup $JENKINS_HOME/jobs/ exists yet $JENKINS_HOME/config.xml does not, so the "compatibility" code kicks in and the old location is used!
Just setting this field to the new value in the instance initializer probably does not suffice, since installations upgraded from before the introduction of this field would be incorrectly switched to the new value.
Probably suffices to adjust the check to also check for the existence of $JENKINS_HOME/config.xml, since most old installations would have saved this file at least once.
- is blocking
-
JENKINS-8446 'builds' directory in a separate location?
-
- Closed
-
- is duplicated by
-
JENKINS-39670 Jenkins changes workspace layout on 2nd startup
-
- Resolved
-
- is related to
-
-
- In Progress
-
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
JENKINS-53284 Changing default layout for workspace and builds should not be a warning for first time startup
-
- Fixed but Unreleased
-