Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Prior to TeamCity 2017.2,  if if you used build chains, there was no easy way to see whether the chain started or not. And if it did, you could not see failed tests and other build problems of the whole chain in one place. In addition, users often created a dedicated build configuration to aggregate artifacts of several builds in a chain and present them in a single place.

...

TeamCity 2017.2 allows you to mark such configurations as Deployment. After that, the builds they depend on, get the dedicated Deployments section on the build results page of this build, allowing you to quickly deploy the build: 

[TODO: Screenshot] Image Added

More details are available in our documentation.

...

TeamCity 2012.2 comes with polished web UI, bringing you the following a number of improvements. In this release, we We also unveil a set of pages which use components built with React and serve data provided by the TeamCity REST API.

...

  • Commit status publisher now supports Git repositories hosted in TFS/VSTS and supports publishing commit as well as pull request statuses.
  • TeamCity now automatically recognizes commits to GitHub, VSTS or Bitbucket and provides links enabling you to view the changes externally, without configuring an external changes viewer per a VCS Root
  • Now you can centrally manage NUnit console versions installed on agents using the Administration | Tools page. Different versions of NUnit 3 can be installed and will be automatically distributed to all build agents.
  • Now the TeamCity server will restart automatically if the Java process of the server crashes.
  • Perforce Stream Depth Support: starting from this release, TeamCity supports deeper directory structure within the root depot: depots with a depth of //DEPOTNAME/1/2/n can be specified in the Perforce Stream field.
  • Experimental support for native SVN checkout has been added
  • Cloud Agent Support enhancements include:
    • Now you can configure a custom URL that the agents cloned from the image will use to connect to the TeamCity server. This URL has to be available from the build agent machine. By default, the TeamCity server URL specified on the Global Settings page of the Administration UI is used.
    • Manual termination: when using cloud agents, you can now choose to stop the instance after the current build using the corresponding new option on the agent page, and the agent will terminate gracefully. It is also possible to force instance termination if required.

Fixed Issues

Previous Releases

What's New in TeamCity 2017.1

...