[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Title: Message Title apgray reopened an issue Jenkins / JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: apgray Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Title: Message Title apgray commented on JENKINS-15751 Re: Cannot escape dollar sign in Windows environment See my comment on JENKINS-13157. It appears if it is a TRAILING $ then two $ characters doesn't work on Windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy commented on JENKINS-15751 Cannot escape dollar sign in Windows environment Hi Gregory, Sorry for the late reply (I don't have access to a windows Jenkins instance at the moment), but I'll use a similar use case to Vincent's: User Story As a Jenkins user I want to use the environment variable name "win_sys_path" with a value "\\127.0.0.1\c$\WINDOWS" So that I can access a windows system folder from a remote computer. User Scenarios Global: Given a Jenkins Windows instance Given the environment variable "win_sys_path" with value "\\127.0.0.1\c$\WINDOWS" When I echo the variable "win_sys_path" Then the value should be "\\127.0.0.1\c" Given the environment variable "win_sys_path" with value "\\127.0.0.1\c\$\WINDOWS" When I echo the variable "win_sys_path" Then the value should be "\\127.0.0.1\c$\WINDOWS" Given the environment variable "win_sys_path" with value "\\127.0.0.1\c\\$\WINDOWS" When I echo the variable "win_sys_path" Then the value should be "\\127.0.0.1\c\$\WINDOWS" Hope that makes sense. Nick 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
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy commented on JENKINS-15751 Cannot escape dollar sign in Windows environment Update: ignore the "Global: Given a Jenkins Windows instance", this same functionality should apply on ALL operating systems (but in this case, specifically on Windows). 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
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Gregory Boissinot started work on JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: Gregory Boissinot (26/Dec/12 6:15 PM) Status: Open InProgress 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
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy created JENKINS-15751 Cannot escape dollar sign in Windows environment Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 07/Nov/12 3:23 AM Description: Fix JENKINS-13566 introduced the following bug. I can no longer escape the dollar sign value on a Windows environment. e.g. foobar1=foo\$bar foobar2=foo$bar Respectively becomes: foo\$bar foo The value "foo$bar" cannot be achieved. My opinion is that the "escaping" behaviour should be the same regardless of operating system. I propose that the JENKINS-13566 changes should be reverted, and that Vincent Latombe should double escape his path. i.e. C:\DOCUME~1*\$NCESE~1\LOCALS~1\Temp Environment: EnvInject 1.71 Project: Jenkins Priority: Blocker Reporter: Nick Grealy 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
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy updated JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: Nick Grealy (07/Nov/12 3:23 AM) Description: FixJENKINS-13566introducedthefollowingbug.IcannolongerescapethedollarsignvalueonaWindowsenvironment.e.g.foobar1=foo\$barfoobar2=foo$barRespectivelybecomes:foo\$barfooThevaluefoo$barcannotbeachieved.Myopinionisthattheescapingbehaviourshouldbethesameregardlessofoperatingsystem.IproposethattheJENKINS-13566changesshouldbereverted,andthatVincentLatombeshoulddoubleescapehispath.i.e.C:\DOCUME~1 * \ * \$NCESE~1\LOCALS~1\Temp 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
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy updated JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: Nick Grealy (07/Nov/12 3:28 AM) Description: FixJENKINS-13566introducedthefollowingbug.IcannolongerescapethedollarsignvalueonaWindowsenvironment.e.g.foobar1=foo\$barfoobar2=foo$barRespectivelybecomes:foo\$barfooThevaluefoo$barcannotbeachieved.Myopinionisthattheescapingbehaviourshouldbethesameregardlessofoperatingsystem.IproposethattheJENKINS-13566changesshouldbereverted,andthatVincentLatombeshoulddoubleescape his their path.i.e.C:\DOCUME~1\\$NCESE~1\LOCALS~1\Temp 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
