Child pages
  • Indore 10 EAP3 (build 41843) Release Notes
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Team Foundation Work Items Tracking

Since TeamCity 10, Team Foundation Work Items tracking is integrated with TeamCity. Supported versions are Microsoft Visual Studio Team Foundation Server 2010-2015, and
Visual Studio Team Services.

TFS work items support can be configured on the Issue trackers page for a project. If a projects has a TFVC root configured, TeamCity will suggest configuring the issue tracker as well.
By default, the integration works the same way as the others (you need to mention the work item ID in the comment message, so the work items can be linked to builds and the links are displayed in various places in the TeamCity Web UI).

Additionally, if your changeset has a related work items,TeamCity can retrieve information about them even if no comment is added to the changeset. Besides, custom states for resolved work items are supported by TeamCity.

Additional options can be enabled via TeamCity internal properties:

  • Related issues linked to TFVC changesets, i.e. commits, can be fetched by setting the teamcity.tfs.workItems.useChangeSets=true internal property. Please, note it is an experimental option and avoid to use it in the production environment.
  • TFS work items workflow can be customized. To display custom resolved states in TeamCity, use teamcity.tfs.workItems.resolvedStates internal property, which set to "Closed?|Done|Fixed|Resolved?|Removed?" by default.

Cloud support

Custom names for VMWare vSphere agent images

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. 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.

Email Verification 

TeamCity administrators can enable / disable email verification (off by default) on the Administration | Authentication page.

If email verification is enabled on the TeamCity server, the Email address field in the user account registration form becomes mandatory. When an address is added / modified,  the users will be asked to verify their it. If the email address is not verified, TeamCity will display a notification on the General tab of the user account settings. Verified email addresses will be marked with a green check on the Administration | Users 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. 

 

 

REST API enhancements

Bundled Tools updates

Other Improvements

  • fixed issues

 

 

 

 

  • No labels