![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2-plugin |
|
Created:
|
09/Jan/15 4:45 PM
|
|
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.
|
|
Environment:
|
Jenkins 1.596
Ubuntu 14.04
|
|
Project:
|
Jenkins
|
|
Labels:
|
slave
ec2
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Jeremy Jongsma
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
