The current version of the plugin counts *all* instances in your account towards the cap, not just the ones that the plugin launched. Do you have other instances in your account? If so, that would cause this problem.
I have a patch in the works to address this problem, but it won't go in until after the 1.18 release, which is still pending. For now, if the number of non-Jenkins-slave instances in your EC2 account is relatively stable, set the global instance cap in the EC2 cloud configuration to that number *plus* the number of slaves you want to allow simultaneously. This is not ideal, but it should work around the problem. ----- Original Message ----- From: [email protected] To: [email protected] At: Mar 28 2013 14:32:52 I have set up Jenkins 1.505 on a server with EC2 plugin version 1.17. The EC2 plugin's home page says that it will automatically start EC2 instance to meet the demand. This hasn't happened for me. I configured my jobs to run on the slaves only. If I manually start a slave on the "Manage Nodes" page by clicking on the "Provision via EC2" link, my jobs can run. But if I don't do this step, the EC2 plugin never starts an EC2 instance for me. >From the EC2 plugin log, I see the following line: Mar 28, 2013 6:19:39 PM hudson.plugins.ec2.EC2Cloud provision INFO: Instance cap reached, not provisioning. I don't know what it means by instance cap. I searched in the config.xml and found that there is a instanceCap of 2 for <hudson.plugins.ec2.EC2Cloud> element and 2147483647 for <templates>. I tried to change these two numbers manually and still my EC2 slaves are not provisioned. Can anyone help? -- 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/groups/opt_out. -- 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/groups/opt_out.
