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

In agent configure, "Remote root directory" can't be recognized when there is any leading space

XMLWordPrintable

      In agent configure page. If "Remote root directory" has any leading blank space, Jenkins can't parse it anymore. For example, "  c:\jenkins-agent" doesn't work but "c:\jenkins-agent" works.

      "  c:\jenkins-agent" was considered as a raw string rather than a file path. The agent starting is also failed because it can't find the root directory.

      The workaround is to NOT include any leading space

        1. windows-path-NO-space-prefix.PNG
          windows-path-NO-space-prefix.PNG
          4 kB
        2. windows-path-space-prefix.PNG
          windows-path-space-prefix.PNG
          10 kB

          [JENKINS-71215] In agent configure, "Remote root directory" can't be recognized when there is any leading space

          Chief created issue -

          Alexander Brandes added a comment -

          Remove the space, then. Paths don't start with a leading space.

          Alexander Brandes added a comment - Remove the space, then. Paths don't start with a leading space.
          Alexander Brandes made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            chiefbugdeveloper Chief
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: