We are using Bamboo OnDemand and EC2 agent. The EC2 instances are being started several times a day. But each start takes more that half an hour. See the logs.
Jun 5, 2013 1:50:15 AM Currently there are no agents that can build: AA-BBB-JOB1. New elastic instance(s) will be started (providing the configuration allows it). Jun 5, 2013 1:50:16 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents. Jun 5, 2013 1:50:16 AM Requested that new elastic instance be created for configuration: Our_main_build_image Jun 5, 2013 1:50:17 AM Elastic instance [i-cedb7ba2] transitioned from STARTING to IDENTIFIED. Jun 5, 2013 1:50:57 AM Elastic instance [i-cedb7ba2] transitioned from IDENTIFIED to RUNNING. Jun 5, 2013 2:20:03 AM An elastic agent is loading on instance: [i-cedb7ba2] Jun 5, 2013 2:23:23 AM Elastic Agent "Elastic Agent on i-cedb7ba2" started on instance i-cedb7ba2
As you can see EC2 instance starts in 40 seconds.
Whereas time betweed "instance RUNNING" and "agent is loading" is 30 minutes!
That is a waste of time and money.
What can be the cause of this 30 minutes lag? How to fix?
You need your private key on your server to do that. I assume you regenerated it? Support will be able to put it back on the server.
You can also use regular AWS Console to get your password if you don't want to store your private key on the server.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs