TeamCity supports cloud build agents using Amazon EC2.
According to "Setting Up TeamCity for Amazon EC2" in TeamCity 8.x Documentation, "Since TeamCity 7.1, if EBS-based instance id is specified in the images list, the instance is stopped instead."
I am using TeamCity Professional 8.0.5 (build 27692).
So, I typed a stopped EBS-based instance id in "Agent images and instances" of Agent Cloud Profile instead of AMI id.
At first, the instance started running when a build was added in Build Queue. After running timeout had been reached, it was stopped.
But, from that time, it did not start running even if another build had been added in Build Queue. The agent clould profile was tagged by "Image Error" that "Image does not exist in Amzon EC2". You can see it in the attached screenshot.
Since what I typed is not AMI id but instance id, the error message is right. But, if I type AMI id, TeamCity creates a new instance using it.
I want for TeamCity not to create a new instance with AMI id but to start running the stopped instance.
How can the same instance be used whenever a build is added in Build Queue?
Any suggestion will be appreciated. :)