Developer tools specialist JetBrains has launched TeamCity 2020.2, including integration with Bitbucket Cloud, Python and JetBrains Space, .NET 5, agentless build steps and new admin features.
According to Alexander Rassokhin, writing for JetBrains, the latest TeamCity has a more privacy-friendly login as well as allowing developers to execute builds in external services without occupying build agents.
TeamCity 2020.2 also unlocks project editing on secondary servers in multi-node setups.
“Administrators can now customise the server clean-up schedule and view disk space usage in external storage locations. And you’re going to love the updates to the new Sakura UI,” Rassokhin writes.
Also, to support more workflows and make the experience with TeamCity smoother, TeamCity now offers support for authentication using external services including GitHub, GitLab, and Bitbucket.
Read the full blog post for all the details and new features.
Marco Behler, blogging for JetBrains TeamCity 2020.2, goes into more detail about agentless builds.
“It is useful whenever you want to call an external service during your builds that does not respond immediately, but takes an indefinite amount of time to run,” Behler explains.
“Before TeamCity 2020.2, such calls would block your build agent while it was waiting for the response from the service.”
For example, third-party deployment services, scripts running on your servers to prepare environments, or services used for manual QA verifications and deployment approvals.
On the TeamCity 2020.2 integration with .NET, JetBrains’ Maria Kudryavtseva and TeamCity .NET developer Nikolay Pianikov say that it follows Microsoft’s .NET 5 software development kit (SDK), which unifies all “modern .NET tools”.
“In anticipation of this, we have revised our integration with .NET in a new build runner that has been available since TeamCity 2019.2.3,” they write. “If you’ve worked with .NET in TeamCity before, you’ll already know that the variety of integration tools it provides can be pretty overwhelming.”
A single .NET runner will ease build composition and testing on multiple OSes by supporting .NET CLI commands, Windows and cross-platform MSBuild, “true” Visual Studio IDE (devenv), Windows and cross-platform tests including NUnit and XUnit, launching Windows, .NET processes and command scripts on different OSes, cross-platform code coverage statistics, and Docker.
“We are still supporting the obsolete runners to give our users enough time to migrate, but this support is limited and we are not going to add any new features to these runners,” they write.
Download TeamCity 2020.2 here.
