* the process of integrating changes becomes a core part of your daily activities,
* integration problems are discovered even before the build is complete,
* you are notified only about the events you are interested in,
* the process of creating builds is quick and transparent.
TeamCity's basic unit of work is a software build. To build your software using TeamCity, you need to have at least one "Build Agent" - a build computer with a set of predefined parameters (such as system and environment variables, JDK version, etc). The build agents are arranged into a build grid. Each software build, in turn, has its own configuration - a set of actions and parameters specified for it. These include the build runner, build schedule, etc. The build agent must meet the builds configuration's requirements: if there is a free build agent that meets the build configuration requirements, the build is started. Otherwise, the build is put into the queue and is processed when a compatible build agent becomes free.
Have a *"10,000-foot look" at TeamCity*, and the IDE's, frameworks, version control systems and means of monitoring it supports. *Point* to a component on the diagram below and jump to its description:
{imagemap:name=[TeamCity Documentation^TeamCitySupports1.png]}
{map:link=[Maven2]|coords=384,29,500,51|shape=rect|title=Maven2}
{map:link=[Ant]|coords=381,6,500,26|shape=rect|title=Ant}
{map:link=[Build Runner]|coords=291,73,375,105|shape=rect|title=Build runners}
{map:link=[Build Runner]|coords=297,224,385,256|title=Build runners}
{map:link=[Ipr]|coords=386,55,503,78|shape=rect|title=IPR}
{map:link=[Duplicates Finder (Java)]|coords=387,80,653,108|title=Duplicates Finder (Java) for IDEA and Maven2 projects}
{map:link=[Duplicates Finder (.NET)]|coords=386,281,690,334|title=Duplicates Finder (.NET) for MS Visual Studio Solutions}
{map:link=[Inspections]|coords=389,103,491,129|title=Inspections}
{map:link=[sln2003]|coords=542,203,591,231|title=sln2003}
{map:link=[sln2005]|coords=541,231,597,253|title=sln2005}
{map:link=[sln2008]|coords=543,259,601,279|title=sln2008}
{map:link=[NAnt]|coords=387,231,478,253|title=NAnt}
{map:link=[MSBuild]|coords=388,209,492,231|title=MSBuild}
{map:link=[IntelliJ IDEA Plugin]|coords=468,374,553,395|title=Installing plugin for IntelliJ IDEA}
{map:link=[Installing Tools]|coords=88,330,242,376|title=Installing tools}
{map:link=[Visual Studio Plugin]|coords=471,402,634,429|title=Installing Visual Studio Plugin}
{map:link=[Eclipse Plugin]|coords=467,349,559,372|title=Installing Eclipse Plugin}
{map:link=[Simple Command Runner]|coords=312,356,452,382|title=Simple Command Line Runners}
{map:link=[Version Control System]|coords=82,396,224,565|title=Supported Version Control Systems}
{map:link=[Notifier]|coords=77,578,309,611|title=Notifiers}
{map:link=[Testing Frameworks]|coords=302,320,450,349|title=Testing frameworks: NUnit}
{map:link=[Testing Frameworks]|coords=299,154,518,205|title=Testing frameworks: JUnit, TestNG}
{map:link=[Perforce]|coords=249,425,461,445|title=Perforce settings}
{map:link=[CVS]|coords=253,450,461,472|title=CVS settings}
{map:link=[Subversion]|coords=250,401,427,419|title=Subversion settings}
{map:link=[ClearCase]|coords=252,500,473,521|title=Rational ClearCase settings}
{map:link=[StarTeam]|coords=252,474,445,499|title=Borland StarTeam settings}
{map:link=[Team Foundation Server]|coords=252,525,546,548|title=TFS settings}
{map:link=[Visual Source Safe]|coords=251,550,464,571|title=Visual Source Safe settings}
{map:link=[My Settings and Tools#watched]|coords=445,567,604,619|title=Watched builds and notifications}
{map:link=\[My Settings and Tools#watched\]\|coords=447,647,608,700\|title=Watched builds and notifications}
...