-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Minor
-
Component/s: core
-
Environment:v2.387.3, Windows 10, Chrome, JDK-17
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