Surely, TeamCity supports Subversion as a VCS which can be used to obtain project sources for your builds. Moreover, for each build TeamCity shows you which Subversion changesets were used to build specific build, which files were added/removed/changed in the build and (in the EAP build of TeamCity) you can even get web-based diff for changed files.
The configuration of your project (including Subversion part) is made using the web interface with possibility to test connection to your Subversion server.
What about Maven2? as i saw teamCity supports Maven2. That's cool. But how strong is this support? Does TeamCity analyse surefire-reports directories? I.e. if I have one project which consists of many modules. And now we have a problem with other tool that if one module fails (i.e. tests fails) we cannot figure out quick the failure and we should use some maven plugins. Maybe TeamCity already has solution for displaying results or even parsing them?
Our support of Maven 2 is really good, and it will be even better in the next release. The uniqueness of TeamCity is that we don't parse report directories and such. TeamCity add own listeners right to the build process and these listeners send build status information while the build is in progress. That means, you're getting detailed reports on what's going on with your build, which tests fail, which step is executed _while the build is in progress_. You'll get notification with failed test and stacktrace before build is finished, as soon as the test has failed. On the web, failed tests are extracted from main build log and shown in a different view (with stacktrace, output and stderr). You can even click on the link "Open in IDE" and this stacktrace will be opened in IDEA for navigation (we're working on Eclipse and Visual Studio support as well). For Maven 2 we actually use Maven2.1 snapshot, because only this version has appropriate API to hook our listeners. This snapshot is bundled with TeamCity so you don't need to install Maven on build agent machines.
Thank you for reply. It seems that TeamCity will have a real strong support for discovering errors, as normally maven2 doesn't report exact error to build console. It's nice to hear about this feature.
Another killer feature is showing build phases in a real time.
BTW how many resources requites TeamCity? I.e. memory size - 100, 200, 300MB for normal performance.
As usual, it depends. It depends on number of buildAgents, number of TeamCity clients, and size of the projects. We at Jetbrains use Xmx500m on TeamCity server (we have several dozens of developers, dozen of projects and up to 20 build agents).