See also Jaipur 2018.1 (build 57605) EAP1 Release Notes

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.

Starting Read-Only Node

A Read-Only node uses the same Data Directory and the same external database as the main TeamCity Server. Therefore, prerequisite of using the Read-Only node is to ensure that it has access to the data directory and database of the main TeamCity Server.

 In addition to the data directory shared with the main server, the Read-Only node requires a 'local' data directory where it stores some caches, unpacked external plugins and some other configuration. By default, the 'local' data directory is automatically created under the <Main Data Directory>/nodes/read_only_node path during the first start. You can override its location using property in the TeamCity start-up scripts.

To start a Read-Only node alongside the main TeamCity Server, do the following:

User Interface Changes

We continue updating the interface:

Trusted HTTPS Certificates

TeamCity now allows uploading a so-called trusted HTTPS certificate - this could be a self-signed certificate, or a certificate signed by a not 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 connections, the certificate had to be imported into Java used by the TeamCity server with help of the keytool utility.

In the final 2018.1 version these trusted certificates will be delivered to agents automatically.

Currently trusted certificates storage is global for the whole server and affects all of the server projects. To upload a trusted certificate, navigate to the Root project administration area and selected Trused HTTPS Certificates menu item in sidebar.

Docker Support

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.

Per-project NuGet Feeds

TeamCity now supports per-project NuGet feeds which could be used by this project and all sub-projects. The introduced NuGet Package Indexer build feature adds NuGet packages published by the build into a specific feed. The default NuGet feed with all packages was moved to the Root project.

Other Improvements