[JIRA] [ec2-plugin] (JENKINS-26369) Allow manual slave launch instead of SSH for on-demand instances

[francisu@gmail.com (JIRA)]

Francis Upton commented on JENKINS-26369

Re: Allow manual slave launch instead of SSH for on-demand instances With version 1.31 if the instance has been previously launched and then stopped, the plugin will automatically start the instance. I'm presuming you are talking about the initial launch here. Is that right? Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[anlutro@gmail.com (JIRA)]

Andreas Lutro commented on JENKINS-26369

Re: Allow manual slave launch instead of SSH for on-demand instances

I'd also like to see this happening. I've pre-configured the AMI which the EC2 plugin uses so that the Jenkins agent gets downloaded and installed on boot, kind of as described here: https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-ConfigureAMIforSpotSupport However, Jenkins still insists on SSHing to the instance, even though it's not necessary. Yes, this is about the initial launch.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[anlutro@gmail.com (JIRA)]

Andreas Lutro edited a comment on JENKINS-26369

Re: Allow manual slave launch instead of SSH for on-demand instances

I'd also like to see this happening. I've pre-configured the AMI which the EC2 plugin uses so that the Jenkins agent gets downloaded and installed on boot, kind of as described here: [https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-ConfigureAMIforSpotSupport] However, Jenkins still insists on SSHing to the instance, even though it's not necessary. Yes, this is about the initial launch.

This ticket is possibly a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-48273

Add Comment