Inspired by a blog post from Roy Osherove – I wanted to be able to fire up additional build agents for peak times.
Yesterday Mario from Codeforce joined me to consult us on how to move Teamcity Agents into Amazon EC2. It took us two hours including lunch 
After our session Mario made a nice blog post on the Topic:
How to run the Build Process in the Cloud with Teamcity and Amazon EC2 « All about Cloud Computing
Now we can build LieberLieber AMUSE even faster
This morning I found a pretty interesting overview provided by Roy on the tools you can use to get your builds maintainable:
The difference between continuous Integration tools and automated build tools
Personally I prefer the Teamcity and MSBuild Variation of Tools.
Wir haben YouTrack jetzt schon einige Zeit als Issue Tracker im Test und werden es auch kaufen! Umso erfreulicher ist das YouTrack 1.0 released wurde. Besonders gefällt uns die einfache Integration mit Teamcity.
If you choose to run Teamcity with a .sln you have an almost automatic integration into Teamcity that can be configured from the web interface.
For most stuff I end up needing a MsBuild Script to get all the Tasks done required for our Builds. If you choose MsBuild as a buildrunner in Teamcity you lose the nice GUI for configurating MsTest . So you need to run the tests by yourself with a simple target in an MsBuild script:
<Target Name=”MsTest”>
<Exec IgnoreExitCode=”true” Command=”"$(VS2008_Path)\mstest.exe" /testcontainer:BridgeTest.dll /resultsfile:BridgeTest.trx” />
<Message Text=”##teamcity[importData type='mstest' path='BridgeTest.trx']“/>
</Target>
The Trick is the Second Task which serves as a Service Message and tells Teamcity to Import the results from MsTest.
Other versions of running MsTest from MsBuild can be found in my previous post.
Mostly the same applies for Nunit Tests – yet you don’t need the Service Message because Teamcity can import Nunit reports from the gui.