First, this isn't really a Jenkins development question, so it belongs on the jenkinsci-users list instead :-)
You didn't mention which version of the EC2 plugin you are using; there have been a number of attempts to reduce the chances of the plugin launching excess slaves due to long startup times. If you look in the Jenkins issue tracker, you'll see that this has been a problem for quite a while with many users experiencing it. There was a patch committed recently (so it will be in the next EC2 plugin release) that will help address this problem, and after that I have a more extensive patch that should cure it completely. ----- Original Message ----- From: [email protected] To: [email protected] At: Feb 12 2013 02:42:07 Hi All, I am having Jenkins 1.437 in my organization which builds on EC2 slave. However due to change in certain firewall policy we are finding it is taking considerable amount of time for a new slave to come online (SSH-SCP-Slave looping back etc ..) Surprisingly Jenkins is firing new VM as first slave which is on verge of coming online is still "effectively offline" ... any clue on how can I instruct Jenkins to wait "a little more" ..... which in due course of time can be parameterized Anticipating your help folks, Soumyak Bhattacharyya -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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 Developers" 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.
