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

Windows paths are no longer correctly passed in the parameters

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      windows 2003 server
    • Similar Issues:

      Description

      When upgrading form the 1.x to the latest 2.x version we noticed that now the backslash characters are interpreted as special characters in the passed parameter value.
      We used to pass our workspace as parameter to the different jobs and now this path gets mangled, so we had to revert the upgrade. Apparently somewhere logic got added to do an interpretation of the value being passed as parameter.
      Could this behaviour be fixed or at least be made so that one can choose if the expansion needs to happen or not.

        Attachments

          Activity

            People

            • Assignee:
              mindless Alan Harder
              Reporter:
              sorokh sorokh
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: