View Source

Read-Only Node

TeamCity makes a step towards High Availability by introducing a read-only mode for a server. It is currently possible to start a second, read-only TeamCity server looking at the same database and data directory as the main one.

The read-only server allows users read operations: view the build information, download artifacts, etc. during the downtime of the main server, e.g. during upgrade.

User Interface Changes

We continue updating the interface:

new build row presentation, featuring the artifacts icon has been added to overview and favorite builds pages
build configuration home page has been re-designed (besides, internally it now uses REST API to show its data)

TeamCity > Jaipur 2018.1 (build 57985) EAP2 Release Notes > image2018-5-22 22:20:33.png

Trusted HTTPS Certificates

TeamCity now allows to upload a so called trusted HTTPS certificate - this could be a self-signed certificate, or a certificate signed by a non well known certificate authority (CA). After that this certificate becomes trusted by TeamCity, which means TeamCity will be able to open HTTPS connections to a resource with this certificate. Previously, to allow such connection the certificate has to be imported into Java used by the TeamCity server with help of a keytool utility.

Trusted certificates are delivered to agents too, for instance if your Subversion server is behind such a certificate, all you need is to upload it to the server and both server and agent will be able to communicate with this server.

Docker Support

Docker support has been added to the for .NET CLI and PowerShell build runners, and these steps can now run in a Docker container.
Docker Build runner has been replaced with Docker Command runner with support for build, push and some other docker commands
AWS ECR (Elastic Container Registry) is now supported by the Docker plugin

Bundled Amazon S3 Support

TeamCity now comes bundled with Amazon S3 plugin, which allows uploading to, downloading and removing artifacts from S3. Resolution of artifact dependencies as well as clean-up of artifacts is handled by the plugin. The artifacts located externally are displayed in the TeamCity web UI.

Viewing Shared Resources Usage

Starting from this build, if at least one resource lock is defined in a build configuration, you can view the resources used by the build on the Shared Resources tab of the Build Results page. The tab displays the resources and their type, including the locks used by the build for each resource.

Clicking the resource name takes you back to the the shared resources configuration page on the project level.

Other Improvements

Now it is possible to use parameter references in agent requirement settings
Users can now hide health report items if they are not relevant for their project (previously only sysadmins could hide them)
Bundled the latest released version of JetBrains .NET Tools (dotCover 2018.1 and ReSharper CLT 2018.1)
The bundled Ant has been updated to version 1.9.11
VSS (Vistual Source Safe) plugin has been un-bundled
All fixed issues