|
||||||||||||||
|
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.
Given that jobs actually can be renamed to contain spaces at the beginning and/or end of the name (unless a sane job name pattern is defined), this is not an issue that can be resolved without addressing those job names first. That's why I'm closing this – there's actually a legitimate use of leading/trailing spaces in the job name reference field that will break when automatically trimming.
FWIW I experienced a lot of headache due to users copy-pasting from Outlook into parameterized jobs' string parameter text fields. I had to resort to providing mostly choice parameters because they couldn't manage trimming the strings themselves consistently. So it's not just job names – and parameters shouldn't be automatically changed in any way for any reason IMO. This weakens this issue further for consistency reasons (why trim one field, but not the other?).
(I'm no particular authority, and my contributions to Jenkins are insignificant, so feel free to reopen if you disagree.)