• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: core, windows-slave-installer-module
• Labels:

  • winsw

[JENKINS-16730] Cannot install Jenkins agent in path with blanks

Markus KARG created issue - 2013-02-09 09:18

Daniel Beck made changes - 2014-10-06 21:35

Component/s		New: core [ 15593 ]
Component/s	Original: slave-setup [ 15929 ]
Labels		New: winsw

Daniel Beck made changes - 2014-10-06 21:38

Priority

Original: Critical [ 2 ]

New: Minor [ 4 ]

R. Tyler Croy made changes - 2016-07-25 23:50

Workflow

Original: JNJira [ 147555 ]

New: JNJira + In-Review [ 176936 ]

Oleg Nenashev made changes - 2016-10-25 11:19

Assignee

Original: Kohsuke Kawaguchi [ kohsuke ]

New: Oleg Nenashev [ oleg_nenashev ]

Oleg Nenashev made changes - 2017-01-08 20:25

Component/s

New: windows-slave-installer-module [ 21834 ]

Oleg Nenashev made changes - 2017-08-15 22:23

Assignee

Original: Oleg Nenashev [ oleg_nenashev ]

Alex Earl made changes - 2022-07-28 21:25

Summary

Original: Cannot install Jenkins slave in path with blanks

New: Cannot install Jenkins agent in path with blanks

Alex Earl made changes - 2022-07-28 21:26

Description

Original: On Windows XP Microsoft had the strange idea to default user profiles in a folder named "Documents and Settings" -- with blanks in it! :-( Jenkins is unable to install a slave in such a folder. The problems seems that the derived service name will then contain blanks, which is not a problem for Windows apparently (one can go to the services GUI and press START, which actually starts the Jenkins slave service), but for Jenkins: Jenkins cannot start that service (will timeout). If 8.3-Support is enabled, one can workaround by providing the abbreviated 8.3 name. But administrators can (and will sometimes) disable 8.3 support. So Jenkins must learn to install a slave in such a folder.

New: On Windows XP Microsoft had the strange idea to default user profiles in a folder named "Documents and Settings" – with blanks in it! :( Jenkins is unable to install an agent in such a folder. The problems seems that the derived service name will then contain blanks, which is not a problem for Windows apparently (one can go to the services GUI and press START, which actually starts the Jenkins agent service), but for Jenkins: Jenkins cannot start that service (will timeout). If 8.3-Support is enabled, one can workaround by providing the abbreviated 8.3 name. But administrators can (and will sometimes) disable 8.3 support. So Jenkins must learn to install a agent in such a folder.