On this page:
The new TeamCity version comes with the experimental UI addressing our customer feedback and aiming at improving your overall experience with the product.
Hide it whenever you want detailed information on a project or build configuration, or keep it open to retain the big picture.
Branches are now split into categories, and you can expand and collapse them as needed. This enables you to keep an overview of your branches and browse them conveniently.
Now, TeamCity can show more about builds on a page, and if you need details on a particular build, clicking it will expand the row allowing more information.
The reworked project overview page provides a compact view of the latest build configurations and subprojects. Build configurations are displayed as tiles and clicking an individual one takes you to the overview of this build configuration.
The new UI is in the experimental stage, and you can switch to it using the icon in the right-hand corner of the screen. There is also a new setting in your profile enabling the experimental UI by default. As not all the features are supported by the new UI, it is easy to go back to the classic TeamCity style when needed.
Canceling Build via Service Message
There can be cases when you need to cancel a build from a script, e.g. a build cannot proceed normally due to the environment, or a build should be canceled form a subprocess, etc. And while it has been possible to use the TeamCity REST API to cancel a build, in this case, the build script ends up being complicated as you need to pass the build ID, the server URL, as well as the authentication parameters (username and password) to the script.
Now TeamCity offers a more elegant way of using a service message to do that: just add a line to your build script telling TeamCity to cancel the build. If required, you can re-add the build to the queue after canceling it:
echo ##teamcity[buildStop comment=‘canceling comment’ readdToQueue=‘true’]
Read more about TeamCity service messages.