Child pages
  • Hajipur 9.1 EAP1 (build 35957) Release Notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

By default, the settings are stored in the .teamcity directory 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 the settings are changed via the user interface, a commit in the VCS will be performed on behalf of the user specified in the VCS root. However, the commit message will also contain the username of the TeamCity user who actually made the change via the UI:

Wiki Markup
{hide-if
:action
=view
}
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:
{code}
//depot/some/path/... => //team-city-agent/...
{code}
{hide-if}

Administrator-defined ordering of projects and build configurations

...

New options should cover the following feature requests:

  • TW-4799 - option for scheduled trigger to do not run a build if artifact-dependency build has failed
  • TW-11553 - option to trigger a build when artifact it depends on changes
  • TW-14975 - option in schedule trigger to run a build with changes corresponding to last successful snapshot dependency build

SSH Agent build feature

This new build feature runs an SSH agent with the selected uploaded SSH key during a build. When your build script runs an SSH client, it uses the SSH agent with the loaded key. You no longer need to manage SSH keys on the agent manually.

The first time you connect to a remote host, the SSH client asks if you want to add a remote host's fingerprint to the known hosts database at ~/.ssh/known_hosts. To avoid such prompts during a build, you need to configure the known hosts database beforehand. If you trust the hosts you are connecting to, you can disable known hosts checks:

  • either for all connections by adding something like this in ~/.ssh/config:
    Code Block
    
    Host *
        StrictHostKeyChecking no
    
  • or for an individual command by running an ssh client with the -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no

...

  • options. You can find more information in the man pages for ssh, ssh-agent and ssh-add commands.

Server shutdown improvements

...

Code Block
stop n
         Sends TeamCity server a stop command and waits up to n seconds for the process to end.
stop n -force
         Sends TeamCity server a stop command, waits up to n seconds for the process to end, kills the server process if it did not stop.

Other Improvements

  • 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)
  • The Run Custom Build dialog allows adding a build to favorites using the corresponding box on the Comments and Tags tab.
  • It is now possible to specify multiple VCS usernames for each level (default, VCS type or VCS root)
  • The default Subversion working copy format has been changed to 1.8
  • SSH Key support for Subversion checkout on agent TW-35092
  • Identify not-actual tests on the Investigations page TW-39494
  • logging preset selected on the Diagnostics page is preserved on server restart
  • fixed issues