File Content Replacer
TeamCity already has a build feature, allowing you to update the
AssemblyInformationalVersion attributes in
AssemblyInfo files of a solution.
Now we have a new build feature, File Content Replacer, enabling you to change a wider range of values for the duration of the build in files specified by the user. It provides value pre-sets for replacement; custom values can also be used. On build finishing, the changed source files are reverted.
Restricting Remote Run in Builds
Using a new build option in the General settings of a build configuration, you can restrict running personal builds. By default, triggering personal builds is enabled; uncheck the allow triggering personal builds option to disable it.
Support for NUnit 3.0
Starting from this EAP, the NUnit Build runner supports NUnit 3.0.
NUnit 3.0.0 Beta 2 supports integration with TeamCity 9.1: NUnit detects if it is run by a TeamCity build agent and automatically switches to reporting test runs using TeamCity server service messages.
Multiple Artifact Directories Paths
By default, TeamCity stores build artifacts in
<TeamCity data directory>/system/artifacts. Starting form this EAP, it is possible not only to configure the artifact path, but also to use multiple paths: the new-line delimited list of paths to artifact directories can be specified on the server Administration | Global Settings page. Absolute and relative paths are supported; the relative paths are relative to TeamCity Data Directory.
If a new build starts, its artifacts are published into the first directory in the list. When looking for artifacts of earlier builds, e.g. when resolving dependencies, TeamCity will go through the list of the artifact directories to locate the required artifact.
Per-branch Versioned Settings
ANSI-style coloring in build logs
TeamCity build logs now support 16 basic ANSI color escape sequences and render clickable hyperlinks:
Merged MSTest and VSTest
- The bundled Ant has been updated to 1.9.5.
- The bundled Java has been updated to version 8.
- PowerShell 5 is now supported
- The TeamCity Web UI now allows specifying custom commandline parameters to pass to dotCover.
- TeamCity REST API adds more abilities to filter builds for the
/app/buildsrequest. For example, now it allows retrieving entire build chains with a single request.