-
Improvement
-
Resolution: Unresolved
-
Minor
-
Jenkins 1.596
Ubuntu 14.04
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.
- duplicates
-
JENKINS-48273 Self-connecting agents
-
- In Progress
-
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?