Starting from this EAP, TeamCity allows storing the project configuration settings in a Subversion and Perforce version control repository. Previously, the only supported version controls were Git and Mercurial.
By default, the settings are stored in the
.teamcity in the root of the repository. If you wish to change the path used by TeamCity, you can create a special VCS Root dedicated to the VCS settings storage, and specify the path as you want there. Note that if settings are changed via user interface a commit in VCS will be performed on behalf of the user specified in VCS root. However commit message will also contain username of the TeamCity user who made UI change.
For example, in case with Perforce TeamCity will use the
.teamcity directory relative to the client you configured; e.g. to store the settings in
//depot/some/path/.teamcity folder, specify the Perforce mapping as follows:
By default, TeamCity displays projects, their subprojects and build configurations on the Projects Overview page in alphabetical order.
Currently each user can define the order to their liking on the Overview page using the up-down button on the Configure Visible Projects pop-up. However, a unified approach might be needed for a team, and now project administrators can apply custom ordering: you can now reorder subprojects, build configurations, and templates of a project on the Project Settings page.
In addition to creating a project from URL, TeamСity now comes with an option to create a build configuration from a VCS URL. All you need to do is enter a VCS URL in the create configuration wizard, select default options to create build configurations and that's it!
- UI improvements including the chains page
- Merged MSTest & VSTest plugins (in progress)
- Support for multiple VCS usernames (in progress))
- Support for Maven 3.3.1
- Support for Gradle 2.4
- Support for Visual Studio 2015 and Microsoft Build Tools 2015 preview in MSBuild and Visual Studio Solution runners, as well as MSTest 2015 (14.0), VSTest 2015 (14.0)
- The default Subversion working copy format has been changed to 1.8
- fixed issues