Hi, thanks for the reply. In your settings do you have a cap on the number of instance you can launch?
Otherwise I am not sure what's wrong since it a very basic setup and there's little in the logs to go on. On Tuesday, January 22, 2013 2:47:56 PM UTC, Kevin Fleming wrote: > > Yes, I use it heavily with my slave templates configured to 'stop' > instead of 'terminate', and the plugin properly restarts the slaves when > they are needed. > > ------------------------------ > *From:*[email protected] <javascript:>*To:* > [email protected] <javascript:>*Date:* 1/20 8:57 > ------------------------------ > > Hi, would log this as a bug but I can't login to jenkins jria (ldap > error). > > The plugin seems to work fine apart from automatically waking up a slave > which is stopped. > > Logs say it want to provision another node, but it should wake up the > stopped node and use that. > > If I go to the node page and start the slave it comes up fine and the job > runs. > > Jenkins - 1.480.2 LTS > Amazon EC2 > plugin<http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin> - > 1.17 > Master with no executors, set to no be used > 1 slave and can only provision 1 aws node > > Anybody use this plugin, with stopped instead of terminate? > > Any help would be great. >
