Child pages
  • Lakhnau 2020.1 RC (build 78421) Release Notes
Skip to end of metadata
Go to start of metadata


On this page:

Downloading full agent with plugins

You can now access a full TeamCity agent, packed with all plugins currently enabled on the server.

A regular TeamCity agent distribution does not contain plugins: the agent downloads them on the first start. The full agent contains all enabled plugins and automatically stays relevant with the current TeamCity server state. This makes its distribution archive larger but significantly reduces the time spent on the first agent run.

The full agent is the most convenient if you use scripts for creating and cloning agent images (for example, in cloud). Each cloned instance will be synchronized with the server from the start and can instantly run a build.

Note that after starting, the full agent behaves like a regular agent. If you modify the state of plugins on the TeamCity server, all active agents will need to restart to sync with the server.

To download the full agent, go to the Agents page in TeamCity, open the Install agent menu, and select Full ZIP file distribution. You can copy the link to this archive and use it in automation scripts; no authorization is required.

Switching TeamCity Server to Java 11

Java 11 has been bundled with the TeamCity server Windows installer and server Docker images instead of Java 8.

TeamCity agents support Java 11 since version 2019.2.

Updates for secondary nodes

With each release, we come closer to providing a full-value TeamCity experience on secondary nodes. This RC brings the following features:

  • Improved support for internal properties
    All secondary nodes now rely both on common internal properties, stored in the shared data directory, and specific properties, configured separately for each node. The node-specific properties have a higher priority and overwrite the common values in case of a conflict.
    To disable any common property on a given secondary node, pass it using the following syntax: -<property_name>.

  • Monitoring cloud agents
    You can access the Agents | Cloud tab to monitor the state of cloud build agents on a secondary node..

Optimizations for TeamCity agent Docker images

To comply with recommended security and performance practices, the TeamCity agent Docker images now:

  • run under a non-root user;

  • use Docker volumes for directories that require writing large amounts of data.

Other improvements

  • The execution conditions for build steps, introduced in our EAP 3 build, now support parameters provided by the build agent. This allows build agents to decide if to execute build steps or not while running the build itself.

  • Disabled cloud agents will not be terminated on matching the terminate condition. This allows for easier diagnostics of cloud instances: you can disable a required agent and inspect its behavior without worrying that TeamCity will terminate it automatically.

  • TeamCity plugin for IntelliJ IDEA allows modifying commit messages of pre-tested commits.

  • Bundled IntelliJ IDEA has been updated to version 2020.1.1.

  • Bundled Ant has been updated to version 1.9.14.

  • Bundled Tomcat has been updated to version 8.5.54.

  • Bundled Maven has been updated to version 3.6.3.

  • Kotlin, used in TeamCity DSL, has been updated to version 1.3.70.

  • Optimized memory usage for servers with lots of test names in the test_names dictionary table.

  • No labels