Child pages
  • Hajipur 9.1 EAP1 (build 35957) 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 4 Next »

Versioned project settings in Subversion and Perforce

Starting from this EAP, TeamCity 9.1 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. 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:

Administrator-defined ordering of projects and build configurations

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.

Create build configuration from URL

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!

  • Support for Visual Studio 2015 build tools (done)
  • Support for multiple VCS usernames (in progress))
  • Merged MSTest & VSTest plugins (in progress)
  • Ui improvements including the chains page

Other Improvements

  • The default Subversion working copy format has been changed to 1.8
  • Support for Maven 3.3.1
  • Support for Gradle 2.4
  • fixed issues
  • No labels