-
Bug
-
Resolution: Fixed
-
Minor
-
None
If you inject a properties file with new line characters it is not parsing these correctly. Also it appears to be treating the properties file and the properties content differently.
To address this issue I submitted a pull request to force parsing as a standard Java properties object and then also extracted the parsing logic to be the same for both the content box and property files.
- is duplicated by
-
JENKINS-38561 Problems occurs on injecting env vars as a build step: Malformed \uxxxx encoding.
- Open
-
JENKINS-20334 envInject leaves in backslash for #, !, =, :
- Resolved
- is related to
-
JENKINS-38607 Wrong parsing of 'property content' drops backslash from string
- Resolved
-
JENKINS-45631 Environment Injector Plugin Doesn't work with the Latest Versions of Jenkins
- Resolved
-
JENKINS-39131 Backslashes are removed from injected environment variables
- Closed
- links to