Restyled TeamCity web UI
Our goal was to make TeamCity web UI more lightweight and more modern looking. This is the work in progress, and we are still working on better readability, information restructuring and so on. However, in general, we consider it finished.
Remote run on changes in branches
We are looking for a more natural way to start remote run builds with distributed version controls. In contrast to usual version control systems in DVCS branches are used extensively. Usually developers implement some feature in their own branch and then push their changes to the master branch in main repository. It is tedious to create separate build configurations in TeamCity server for each such branch. Now we have a better solution.
If you are using Git or Mercurial in you project you can add special build trigger called "Branch Remote Run" to a build configuration. This build trigger will watch for commits into the branches of this build configuration VCS roots. If a commit is detected and if branch name matches to some specific pattern, trigger will add personal build to the build queue.
Tracking of build configuration and project changes in audit
Audit log finally is able to track changes in the project and build configuration settings. In the project or build configuration administration pages you can now see the name of the user who modified project or build configuration, as well as a link to the changes themselves. Since project and build configuration settings are stored on disk in plain xml, the link will just open the usual TeamCity diff window showing changes in these xml files.
Build steps administration
Build steps have got names. Now it is possible to add a description to each build step, and this description will be shown in the build steps lists. Also you can now easily copy build step to any accessible build configuration.
Default parameters for all of the project build configurations can now be specified on the Project parameters tab.