|
||||||||||||||
|
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/d/optout.
The feature already exists as mentioned in the comments.
There's no reason to prohibit spaces on an instance running only well written scripts and programs able to handle spaces or whatever other craziness can be used in job names. Additionally, there are item types that aren't projects running scripts (mostly added in plugins), and those can usually handle spaces in their names without any problem no matter how they're otherwise configured.
As Jenkins cannot decide this manually, it's the job of the admin to figure this out and configure Jenkins accordingly.