As per description, the Amazon EC2 allows to set slaves to be stopped rather than terminated so their state is preserved and can be reused.
Unfortunately that does not seem to work at all. Once my On Demand node is stopped (either manually or due to idle timeout), subsequent build start creates completely new instance based on selected AMI. However, if I launch the node manually via Manage Nodes, instance on EC2 will be resumed and subsequent build start will reuse this instance instead of creating new one. Is it somehow possible to configure Jenkins to resume instances on EC2 automatically? -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Amazon-EC2-plugin-does-not-resume-stopped-instances-tp4700115.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
