Build Grid
TeamCity uses a pool of Build Agent computers to simultaneously create multiple builds of your projects. All these Build Agents are managed from the single TeamCity server and the build results can be obtained in real time, while builds are running. We call this technology the Build Grid.
Multiple Build Agents
Build Agents are computers on the company's network capable of running builds which altogether make up the Build Grid. Depending on the project's or company's needs, they can use different operating systems and platforms, have some predefined parameters that make it compatible for creating certain types of builds and testing certain changes.
As developers integrate their work results into the Version Control System, the TeamCity server distributes them to the Build Agents automatically, so there is no need to install version control software on all of your build agents.
Build Agents' Workload Statistics
More visual metrics, namely, statistics of Build Agents' activity and their usage during a particular time period are now available.
We are sure you'll find this feature helpful in:
- your daily administration activities for lowering your company's network workload
- finding and eliminating the gap between the most frequently used computers and those which are often idle
- reducing the cost of your hardware resources ownership
"Time to fix tests" Statistics
A new type of statistical data display: time it took to fix the build's tests.
Agents Management UI and Security
After the installation of Build Agent software, the Build Agents are primarily managed from the web UI.
The Agents tab provides information on the Build Agents, their availability, current status and properties.
In TeamCity 3.0 only authorized Build Agents can run builds. To authorize a Build Agent, or to enable/disable it, a user needs to have the corresponding permission, which is assigned by the TeamCity system administrator.
Agents Auto-Upgrade
Build Agents upgrade themselves automatically saving the system administrator's time and lowering the cost of TeamCity ownership.
Multi-platform Builds
TeamCity's Build Agents can have different platforms, operating systems and pre-configured environments that you may want to test your software on.
No VCS setup on Build Agents
To be capable of getting project sources, Build Agents are not required to have any pre-configured Version Control System on them.
Assigning Builds to Particular Agents
To get faster feedback on the integration results of certain changes, lower the number of builds in the Build Queue and manage the Build Agents' workload more effectively, TeamCity 3.0 introduces a new run policy: you can explicitly limit the build configurations which can run on a particular Build Agent. Previously, all build configurations compatible with a Build Agent were allowed to run on it (this is the default policy). Go to the Compatible Configurations tab on the Build Agent page to specify the corresponding run policy and build configurations.
It is now possible to assign the build either to a particular Build Agent or to the fastest available Build Agent, right from the Projects page.
Build Start Time Estimation
In TeamCity 3.0 you can see approximately when your build will start on the Build Queue tab, in the Time to start column. You can also see the prediction of the build duration time and name of the Build Agent which is supposed to run it.
Time in Build Queue Statistics Chart
To help you evaluate trends in your Build Agents' performance, TeamCity 3.0 provides a special chart showing the time the build of particular build configuration spent in the Build Queue. This information is useful in deciding when additional build agents should be installed.
