|
||||||||
|
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.
So it looks like backslashes are not exactly valid, but Perforce does allow adding paths with backslashes to the stream configuration (it just ignores them). I still think it might be worth investigating and possibly coming up with a fix, because even if someone accidentally entered in an "invalid" path, it's bad that it can actually break a working Jenkins environment. I'll leave it up to you, though, if you think it's worth creating a new issue. Sorry to hijack this thread somewhat, although actually in the subfolder right below where I was having this problem, I did need the patched build as I had folders with matching brackets and a dash between them. Thanks for all your help!