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

A recent update breaks builds by escaping slashes to percent signs in workspace paths

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.1.2

      Description

      After a recent update, slashes in git branches (e.g. bugfix/branch-description) are escaped into workspace path names using %2F, as in wkspacepath/bugfix%2Fbranch-description. This breaks the build on my windows machine. The slashes used to be translated to underscores.

        Attachments

          Issue Links

            Activity

            Hide
            smorley Stephen Morley added a comment -

            This problem appeared after I did an upgrade. I tried to restore to previous version and plugins but problem persisted. I enabled a log as noted above and found a message: JENKINS-2111 path sanitization ineffective when using legacy workspace root directory c:\JenkinsWorkspace\${ITEM_FULLNAME}; switch to ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}

            so I did and its working now!

            This did move to a new workplace so all the directories are now so I don't know if that fixed it or the form of the path. Note the slashes were reversed. Before this Jenkins was creating a working directory simply with the first part of the name , e.g. QA/V2018 became QA

            Show
            smorley Stephen Morley added a comment - This problem appeared after I did an upgrade. I tried to restore to previous version and plugins but problem persisted. I enabled a log as noted above and found a message: JENKINS-2111 path sanitization ineffective when using legacy workspace root directory c:\JenkinsWorkspace\${ITEM_FULLNAME}; switch to ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} so I did and its working now! This did move to a new workplace so all the directories are now so I don't know if that fixed it or the form of the path. Note the slashes were reversed. Before this Jenkins was creating a working directory simply with the first part of the name , e.g. QA/V2018 became QA
            Hide
            jglick Jesse Glick added a comment -

            Stephen Morley you may have hit JENKINS-21942. Note that this only affects builds run on the master, not on agents.

            Show
            jglick Jesse Glick added a comment - Stephen Morley you may have hit JENKINS-21942 . Note that this only affects builds run on the master, not on agents.
            Hide
            smorley Stephen Morley added a comment -

            Jesse Glick that might explain why the setting was not updated but why is it not valid to reference a directory outside of the JENKINS_HOME. Personally I don't like keeping active data sets in the "Program Files (x86)" directory. This has worked for over 5 years now and suddenly it fails. (Turns out we also have a problem with some utility which is not working with the spaces in the path name so our builds are broken using this form but without it Jenkins just chokes).

            Show
            smorley Stephen Morley added a comment - Jesse Glick that might explain why the setting was not updated but why is it not valid to reference a directory outside of the JENKINS_HOME. Personally I don't like keeping active data sets in the "Program Files (x86)" directory. This has worked for over 5 years now and suddenly it fails. (Turns out we also have a problem with some utility which is not working with the spaces in the path name so our builds are broken using this form but without it Jenkins just chokes).
            Hide
            jglick Jesse Glick added a comment -

            Actually that warning was really intended for the broken old default ${ITEM_ROOTDIR}/workspace. Customized roots ending in …/${ITEM_FULLNAME} (or …/${ITEM_FULL_NAME}) should be supportable with the new managed layout. Again note that this only pertains to master-based builds; using agents is recommended.

            Show
            jglick Jesse Glick added a comment - Actually that warning was really intended for the broken old default ${ITEM_ROOTDIR}/workspace . Customized roots ending in …/${ITEM_FULLNAME } (or …/${ITEM_FULL_NAME }) should be supportable with the new managed layout. Again note that this only pertains to master-based builds; using agents is recommended.
            Hide
            jglick Jesse Glick added a comment -

            PR 137 should fix the issue discovered by Stephen Morley. I never got diagnostics from the original reporter Øyvind R so hard to know if that issue was the same or unrelated.

            Show
            jglick Jesse Glick added a comment - PR 137 should fix the issue discovered by Stephen Morley . I never got diagnostics from the original reporter Øyvind R so hard to know if that issue was the same or unrelated.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                godskalk Øyvind R
              • Votes:
                2 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: