We have just been building some EC2 server images for Windows/VS2012 CI servers triggered through bamboo (see http://davidstringeratwork.wordpress.com/2012/10/04/using-atlassian-bamboo-ondemand-for-visual-studio-2012-projects-part-1/). We built an AMI image of the CI server and configured bamboo to launch that when we committed to GITHub.
We encountered a problem when we added some other, non-transient instances to help with specialist testing. At that point, our automated CI builds would no longer trigger. We were helped out by the support folks to identify that the problem related to the "number of elastic instances on your AWS account that are not controlled by Bamboo does not exceed" setting in the bamboo configuration. Once we had some more running instances we had exceeded this value so bamboo would not launch any more instances, even though the instances were for different purposes.
The question is this: should this bamboo configuration setting not just relate to instances started from AMI images are launched by bamboo rather than all instances regardles of the AMI from which they originate? Is there something we are missing here in terms of a problem the current behaviour is solving that we haven't encountered yet?
The question is this: should this bamboo configuration setting not just relate to instances started from AMI images are launched by bamboo rather than all instances regardles of the AMI from which they originate?
It's a failsafe measure. Some cases to consider:
Interesting. For our own current purposes (running CI servers) I would never think of running a stock image but I can see that for people who do use stock images rather than custom that this could be an issue. Even so, I think that all of these cases woudl be improved if there was a way of telling bamboo (or bamboo working it out) which image types it can (or has been able to) launch and only including these in the count.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot