|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
When collecting your requested data, I found there is a totally different root cause. We have that command in a batch file, and Windows interprets the %2 from the escaped blank as batch parameter, replacing it with an empty string. Escaping with another percent sign in the batch file (i.e. blank%%20name) fixes everything.
So basically there is no bug in Jenkins. However, everyone just copying the command line of a slave with a blank in the name will easily run into the same trouble. Maybe a note could be added to the slave page? I'm fine if you just close the bug.