Child pages
  • Hajipur 9.0 EAP1 (build 31423) 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 9 Next »

Versioned Project Settings

Starting from this EAP, you can now enable the two-way synchronization of your project settings with your version control. When the synchronization is enabled, each administrative change you make to the project settings in the TeamCity Web UI is committed to the version control. If you change the settings in the version control, the TeamCity server will detect the changes and apply them to the project on the fly.

Enabling synchronization for the project also enables it for all the subprojects. TeamCity synchronizes all changes to the project settings (including modifications of build configurations, templates, VCS roots, etc.) with the exception of SSH keys. The project settings will be stored in the .teamcity folder in the repository.

(warning) Be aware that as soon as synchronization is enabled in a project, TeamCity will make one commit for this project and one for each of its subprojects to import the current settings. You may see a really big number of commits for a large project.

You can enable synchronization on the Versioned Settings page of the project administration.

TeamCity will not only synchronize the settings, but will automatically display changes to the project settings the same way it is done for regular changes in the version control.

Sreenshot of changes

Known Limitations

  1. At the moment the only supported version control is Git.
  2. When running a history build in TeamCity, the current project settings will be used.
  3. Project settings may contain scrambled passwords. Fro security purposes, we recommend storing your project settings separately from your project sources (in a different more secure repository).

Build Time Report

Now you can see the comparative statistics of build time for projects and build configurations: the Build Time report is now available in the Project-related Settings of the TeamCity Administration area.

The report displays total build duration within the last 24 hours for the server and individual projects (the default settings) with the percentage in relation to the parent project. The scope can be further drilled down to th build time of an individual build configuration (with different shades of gray indicating the hierarchy):

The grouping and the period settings can be modified.

Test Invocation Count

branch filter for notifications and charts

  • faster backup / restore - vcs_changes refactoring - VCS instances calculation I s faster

Unicode Support for MS SQL and Oracle

The national character sets (nchar, nvarchar, nclob types) for text fields are now supported in MS SQL and Oracle databases used by TeamCity. You can now use Unicode characters in the following fields in TeamCity:

  • TeamCity user names (not logins)
  • VCS committers' names
  • VCS commit descriptions
  • file names
  • build status text
  • tags (on promotions and builds)
  • test names
  • mute and investigation comments
  • values of environment variables received from agents (in the agent types)
  • audit comments

Meta-runner Import

To share a meta runner with someone, you can now use the Upload button on the Meta-Runner tab of the project administration where you can select an XML definition of a meta-runner from the file system.

ability to set tags for queued / running builds

Plugin dependencies

Other improvements

  • Vs Addin supports Resharper 8.2 and dotCover 2.7
  • fixed issues (\{9.0+EAP1\}+tag%3A+-\{trunk+issue\}+-\{Gaya+8.1+%2829879%29\}+-\{Gaya+8.1.1+%2829939%29\}+-\{Gaya+8.1.2+%2829993%29\}+-\{Gaya+8.1.3+%2830101%29\}+-\{Gaya+8.1.4+%2830168%29\}+-Task+sort+by%3A+\{issue+id\}+asc)
  • No labels