TeamCity On-Premises 2021.1

Improved Building and Testing:

• Kotlin script build runner - Added new Kotlin script build runner. It is cross-platform, supports importing external libraries and can be used in most places where you currently use the Command Line build runner.
• Node.js build runner - Added a new Node.js build runner that provides first class support for building your web applications. It supports npm and yarn, can work with public and private registries and automatically detects build steps based on package.json. Just like with all other build runners in TeamCity, you can run your builds inside a Docker container and set them up using a Kotlin-based configuration.
• Thread dumps for Docker-based builds - You can now view thread dumps of Java processes running in Docker containers on any operating system. For Linux-based Docker containers, you can also see the list of other running commands and their parameters.
• In addition to the new Kotlin and Node.js build runners and thread dump viewing improvements, this new version features improved ReSharper Inspections and Duplicates Finder build runners which are now cross-platform and can run in Docker.

Improved Perforce integration:

• Improved commit hooks setup - You can now set up commit hooks and have your builds automatically triggered by installing only one single script on the Perforce server.
• Perforce workspace cleanup - TeamCity now provides manual and automated clean-up of the Perforce workspaces created by the TeamCity server.
• ChangeView specification support - You can now limit the VCS root scope to particular revisions with the use of the ChangeView specifications. Usage of the @revision syntax in the import statements of Perforce stream definitions is now also supported.

Hardening the security of your CI:

• Greater security with improved access tokens - This release allows you to generate access tokens that are limited in time and scope. You can now grant scripts, that interact with the TeamCity API, just enough rights to do their job, without the fear of giving them too much power. You also no longer have to remember to revoke their access after they finish.
• Separate permission for personal builds with patches - TeamCity now has a separate permissions for running personal builds with custom patches. This helps you ensure that all code executed on build agents is authored only by trusted users.

Improved configurability:

• Trigger-defined parameters - Your build triggers can now define custom parameters to enable or disable build steps, or change what happens inside your build scripts. For example, your nightly builds can now be different from the builds triggered by version control check-ins, all within the same build configuration.
• Git shallow clones - You can now enable Git shallow cloning and check out the latest version of source code with depth=1, without creating local Git mirrors. This will be particularly useful for companies that spin up clean, short-lived build agents in the cloud for every build.
• Multiple VCS triggers support - You are no longer limited to only one VCS trigger per build configuration. TeamCity now allows adding multiple triggers with different rules and with different branch filters.
• Disabling UI editing - Added a new option that will allow administrators to prohibit editing project configurations through the UI if they are set up using Kotlin.

Improved availability:

• Switching main node responsibility in runtime - To allow for high availability and minimize the downtime during maintenance, TeamCity 2021.1 introduces the new “Main TeamCity node” responsibility that can be transferred to a secondary node in runtime. When you do it, the secondary server becomes the main node and automatically receives all of the main node’s responsibilities, including processing builds and managing build agents.
• Controlling the number of builds on secondary nodes - TeamCity now allows you to define the share of builds that will be processed by its nodes. This helps you make sure that every server takes just the right amount of the build processing load and doesn’t exceed its hardware capabilities.
• Elastic-based search - Previously, every TeamCity node had its own search index that was stored locally. This release provides an alternative search engine based on Elasticsearch. It has a distributed index, consumes less disk space and works more efficiently in multi-node installations.

Improved Sakura UI:

• Improved the Sakura UI, making it faster, easier to use and supporting all workflows from the classic UI. This new version brings a UI Assistant that shows new users how to navigate around the interface, improvements to the Build Status widget, updates to the Build Overview page, project hierarchy views, and more.