[
https://issues.jenkins-ci.org/browse/JENKINS-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159057#comment-159057
]
francis Upton commented on JENKINS-5850:
----------------------------------------
Could this be happening because you are running Jenkins on Windows and
launching Linux EC2 instances? I don't see any special code in the ec2-plugin
that does this, so maybe it's something in the UI stuff that we need to account
for in the ec2-plugin (make up the differences in the newlines). When Windows
is supported as EC2 instances we will need to convert the \n (if Jenkins is on
Linux) to \r\n.
> EC2 plugin init script field inserts \r\n between lines
> -------------------------------------------------------
>
> Key: JENKINS-5850
> URL: https://issues.jenkins-ci.org/browse/JENKINS-5850
> Project: Jenkins
> Issue Type: Bug
> Components: ec2
> Reporter: larsko
> Assignee: Kohsuke Kawaguchi
> Priority: Minor
>
> The EC2 plugin adds Windows newlines \r\n between lines entered into the
> "Init Script" box for an AMI. When this is executed on the slave, the line is
> broken at \n and the command is left with a trailing \r, which causes the
> command to fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
