In the previous EAP, Agent Cloud profile configuration was moved from the server level to the Root project level. Now cloud agent profiles configuration is also available at the project level, allowing Project administrators to configure their own cloud profiles without bothering System administrators.
When configuring a cloud profile, the project administrator can select an agent pool to assign the cloud agents to: it is possible if the pool contains this project and/or its subprojects only. Pools containing projects other than the current one and its subprojects will not be available for assignment. If the assigned pool is changed in future so that the criteria is not met or if the agent pool is not specified, the cloud agents will be assigned to a special read-only pool containing only this project and its subprojects.
The idea is to restrict the cloud agents pool only to a given project with its subprojects to track cloud costs by project.
Note that if you use Kotlin DSL for your TeamCity Root project settings, you need to update your DSL as described in the DSL Upgrade document.
Modified settings for changes calculation
The Display settings section of the VCS Root checkout options for a build configuration has been renamed into Changes calculation settings (1), featuring a new option to exclude the default branch changes from other branches (2).
A new section, Default branch settings (3), has appeared. By default, TeamCity will run builds in the default branch. If this behavior is undesirable, you can uncheck this box and the default branch will not be shown in the UI. This can be useful if you want to build pull requests only.
Note that unchecking the option will affect all the aspects concerning the default branch, including:
- build chains: if a chain is triggered in a branch, and this branch does not exist in one of the configurations that is a part of the chain, previously TeamCity fell back on the default branch. If the default branch in this configuration is not allowed, building the dependency will fail
- the behavior of the Run dialog: the run custom build dialog will be displayed asking to select a branch
- triggers and notifications.
Web UI improvements
Breadcrumbs have been redesigned - the breadcrumb trail is displayed in a smaller font compared to the large font of the current item title. Hovering over the icon next to the title displays an arrow, prompting to click for quick sibling navigation:
New Fast Selectors
The new TeamCity version boasts of new selectors, such as branch selector in various places in the UI and the build configuration selector on the Dependencies page for a build configuration:
The new selectors ensure better performance with a large number of build configurations and branches.
The Snapshot dependencies section on the Dependencies page for a build configuration now allows previewing the build chain and its configuration:
The preview shows builds of the chain; the builds with automatic triggering configured are marked with the icon:
Also, the dependencies tabs allow grouping/ungrouping builds and highlighting the builds reused from previous chains (suitable builds).
Override build features and failure conditions
TeamCity now supports overriding of build features and failure conditions inherited from a template.
Installing IntelliJ Inspections and Duplicates Engine Centrally on Agents
Now you can easily distribute to/ remove from all agents different versions of the JetBrains IntelliJ Inspections and Duplicates Engine centrally using the Administration | Tools page. The page displays the installed versions as well as engines usages in build configurations. The bundled version is set as default. You can install other versions and change the defaults.
Starting from this EAP, TeamCity provides experimental support for PowerShell on Linux and Mac OS. To give it a try, download a PowerShell package for your platform and set the
teamcity.powershell.crossplatform.enabled property to
true for the agents you want to try PowerShell on.
The bundled Java has been updated to version 8u121.
Numerous bugs have been fixed in the NuGet feed
TeamCity now supports publishing of NuGet packages to TeamCity from NuGet Publish build runner.
TeamCity supports NuGet 4.0 now
A new server health report helps to find agents which failed to upgrade.
- File content replacer supports .NetCore csproj files
- All fixed issues