|
||||||||
|
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/groups/opt_out.
It sounds like your configuration is set up correctly. As you state, the issue is your non-public Jenkins master.
Since jnlp requires the slave to connect to the master, it will not be possible for the instance to find the master and connect to it. Since currently the only way to launch Spot instances through the plugin is with jnlp, I don't think this will be easily fixable.
The alternative is to give an option to launch the Spot instances in the same manner as On demand instance in which the Jenkins master connects to the slave. This would result in Jenkins polling EC2 frequently on the initial start up of a Spot instance to determine when there is a usable instance. Also if a persistent bid is used, and the Spot instance was terminated, the instance might eventually restart, but Jenkins would not know about it.