Details
-
Improvement
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
Jenkins 1.596
Ubuntu 14.04
Description
The EC2 plugin requires launching slaves via SSH for on-demand instances. Due to various connectivity issues that have been reported with the SSH slaves plugin (and which I am experiencing constantly), I'd like to use an AMI that does its own connection to Jenkins master based on EC2 user-data.
The only change needed to support this would be a configuration option that allows me to tell the plugin to treat the on-demand instances like spot instances in terms of launching the Jenkins slave.
Attachments
Activity
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
Andreas Lutro
added a comment - - edited 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 
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?