|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Allowing jobs with spaces in names does complicate things, making it harder (but not impossible) to handle via script. I prefer not to allow any spaces using "Create Job Advanced" plugin to enforce some common rules.
To allow spaces, basically any path that contains the job name should be enclosed with double quotes either on variable assignment as well in usage. Since command "find" doesn't like to have wildcard enclosed in double quotes, that can be split into first a change directory and then the find command with wildcard. I uploaded new versions of scripts but it didn't seem to have replaced the old ones when uploaded, so refer to the most recent ones.
Jenkins on Windows also seems to have a different behavior since it doesn't seem to use any symbolic links (not visible on cygwin anyway with 1.484), so the the link related checks probably are not applicable on Windows.