I am tasked to improve quality and implement TeamCity for continuous integration. My experience with TeamCity is very limited – I use mostly TFS myself and have some experience with CC.NET.
A lot should happen within a build process… actually the build is already pushed into three different configurations that will run one after the next.
My main problem is that in each of those I actually would need to start multiple runners. For example, the first build step shall consist of:
- The generation of new AssemblyInfo.cs files for consistent in assembly numbering
- The actual compilation
- A partial unit test run (all tests that run fast and check core functionality)
- An FxCop run
- A StyleCop run
The current version of TeamCity only allows to configure one runner … which leaves me stuck with a lot of things.
How you would approach this? My current idea is going towards using the MsBuild runner for everything and basically start my own MsBuild based script which then does all the things, pretty much the way that TFS handles it (and the same way i did things back in the cc.net way with my own Nant build script).
On a further problem the question is how to present statistical information, for example from unit tests running in different stages (build configurations). We have some further down that take some time to run and want that to run in a 2nd or 3rd step (the latest for example testing database generation code which, including loading base data, takes about 15+ minutes to run). OTOH we would really like test results to be somehow consolidated.
Anyone any ideas?
Thanks.
TeamCity 6.0 allows multiple build steps for a single build configuration. Isn’t it what you’re looking for?