For me, TeamCity (7.0.2) successfully deploys the EC2 virtual machine from the user AMI, starts our build and sends back the build artifacts.
However, even when I did this with older versions of TeamCity, I was always unhappy with the notion that it simply terminates the instances after they are completed, and then creates new instances using the configured AMI the next time the build agent is needed.
Can I get TeamCity to run stop commands and then start commands instead? It has tons of advantages - faster turnaround time, allowing named instances in agent statistics, and saving the Mercurial clone for EBS for the next build are just three.
ps I suppose I could use chained assemblies to directly access the EC2 API and not use the native cloud support, but that sounds like a lot of work and seems flaky
source
share