|Table of Contents|
Project Settings Configuration Changes
Starting from this EAP, configuration of issue trackers, versioned settings, custom charts and shared resources was moved from
<TeamCity Data Directory>/config/projects/<ProjectID>/pluginData/plugin-settings.xml to
<TeamCity Data Directory>/config/projects/<ProjectID>/project-config.xml file. The file now has the
<project-extensions> element which contains all of the above-mentioned project features.
For each feature an <
extention> sub-element is added. An extension must have a unique id in the project, its type attribute defines the setting (
IssueTracker, buildtype-graphs/project-graphs; versionedSettings, JetBrains.SharedResources). Each extension is described by the <
parameters> element containing
<param> sub-elements with
Team Foundation Work Items Tracking
In addition, resolved states in TeamCity can be customized by using the
teamcity.tfs.workItems.resolvedStates internal property set to
"Closed?|Done|Fixed|Resolved?|Removed?" by default.
VMWare vSphere Custom names for
The names of virtual machines in VMWare must be unique. When using the same image in different cloud profiles, to avoid possible conflicts, use the custom agent image name when configuring a cloud profile in TeamCity. This feature can be also useful with naming patterns for agents. When a custom agent image name is specified, the names of cloud agent instances cloned from the image will be based on this name.
Amazon EC2 Custom instance tags
Custom tags can now be applied to EC2 cloud agent instances: when configuring Cloud profile settings, in the Add Image/ Edit Image dialog use the Instance tags: field to specify tags in the format of
<key1>=<value1>,<key2>=<value2>. Amazon tag restrictions need to be considered.
TeamCity administrators can enable / disable email verification (off by default) on the Administration | Authentication page.
When project import scope if configured, users with the same username and email are compared based on their email verification. TeamCity will display the conflicts information and the administrator can choose whether to merge the users found.
Agent Limit for Pools
By default, an agent pool can contain an unlimited number of agents. Since TeamCity 10.0, you can set a maximum number of agents in the pool (not applicable for the Default Pool). If the maximum number of agents is reached, TeamСity will not allow adding any new agents to this pool. This includes moving agents from other pools and automatic authorization of cloud agents. New cloud agents will not start if the target pool is full.
REST API enhancements
Bundled Tools updates