Professional mode restrictions
We decided to remove all of the Professional mode restrictions except one: the maximum number of build configurations. We've done that to simplify TeamCity evaluation in the small teams, and to simplify transition from the Professional to Enterprise version. Also those who want to write Authentication plugin for TeamCity do not need Enterprise version anymore.
Tests Investigation and Muting
New type of notification for tests muting / unmuting was added.
Improved user interface
User interface has been improved. Investigation and mute actions are now always visible, in both bulk and single test mode.
Under the Agents tab you can now see new addition - Agent Push. This is the functionality we've developed for quite some time, and now we consider it is ready to be released.
In brief, this is a new way to install build agents on the machines in your network, or in the cloud. The agent distribution is pushed on a Unix machine (by SSH) or on a Windows machine (with help of psexec), installed there, and is started automatically. For this to work, TeamCity needs to know credentials of the user on a remote machine. Also since TeamCity is using Sysinternals psexec, push of the agent on Windows machine is only possible if server is installed on Windows.
This feature also integrates with Amazon Cloud functionality. You can create a preset for Agent Push, and specify this preset in Cloud profile settings. In this case, when TeamCity starts an image in the cloud, the agent is pushed on the image automatically, so you do not need to install it on the image and modify build agent configuration to specify correct server URL.
Remote Run on Branch improvements
In previous EAP build, remote run on a branch trigger required from the developer to specify TeamCity username inside the branch name. This was TeamCity understood who will be the owner of the personal build from the branch. We improved it and TeamCity now can create personal build on the name of the last committer to the branch. This seems to be much more convenient way for the developers. All they should do now, is to specify correct prefix or suffix for the branch name. The rest is done automatically.
PowerShell is quite popular tool for Windows developers. We already had separate plugin for it, but now we decided to bundle it with TeamCity.