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

JENKINS_HOME deleted when Custom Workspace is ..

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • Jenkins ver. 2.138.1
      Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-134-generic x86_64)
      Full [^systemInfo.txt] attached.

      Thanks to JENKINS-17818 when a relative path is specified for Custom Workspace the resulting workspace path is relative to JENKINS_HOME instead of the default workspace location ${ITEM_FULL_NAME}/workspace as I had expected.

      The consequence of specifying a relative path of .. for Custom Workspace is that the workspace is set to ${JENKINS_HOME}/.. which Jenkins attempted to wipe out when commencing the Job.

      End result is apparently much the same as seen in JENKINS-9806, dozens of jobs configurations, workspaces, build logs, jenkins credentials, ssh keys and so on all recursively deleted.

       

          [JENKINS-53918] JENKINS_HOME deleted when Custom Workspace is ..

          Daniel Beck added a comment -

          Can this problem occur when not building on master as recommended (e.g. here: https://wiki.jenkins.io/display/JENKINS/Security+implication+of+building+on+master ), which is inherently unsafe?

          Daniel Beck added a comment - Can this problem occur when not building on master as recommended (e.g. here: https://wiki.jenkins.io/display/JENKINS/Security+implication+of+building+on+master ), which is inherently unsafe?

            Unassigned Unassigned
            gb96 Greg Bowering
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: