Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21942

Unreliable defaulting of Jenkins.workspaceDir

      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.

          [JENKINS-21942] Unreliable defaulting of Jenkins.workspaceDir

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-8446 [ JENKINS-8446 ]

          Jesse Glick added a comment -

          Seems like Jenkins 1.420 is the last “old version”.

          Jesse Glick added a comment - Seems like Jenkins 1.420 is the last “old version”.
          Daniel Beck made changes -
          Link New: This issue is related to SECURITY-129 [ SECURITY-129 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154019 ] New: JNJira + In-Review [ 178658 ]

          Jesse Glick added a comment -

          Should be rechecked in 2.x after changes relating to the installation wizard, which might have forced a save.

          Jesse Glick added a comment - Should be rechecked in 2.x after changes relating to the installation wizard, which might have forced a save.

          Daniel Beck added a comment -

          Well, there's always -Djenkins.install.runSetupWizard=false for the chefs among us.

          Daniel Beck added a comment - Well, there's always -Djenkins.install.runSetupWizard=false for the chefs among us.
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-39670 [ JENKINS-39670 ]

          Jens Keller added a comment -

          this seems to be open for quite a long time - any updates?

          Jens Keller added a comment - this seems to be open for quite a long time - any updates?
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-38837 [ JENKINS-38837 ]

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            5 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated: