The JetBrains Blog

We’re happy to present the new release today, Kotlin 1.3.40. In addition to the quality and tooling improvements the main focus for this version has been on: Gradle support for NPM, Yarn, and Webpack for Kotlin/JS Test runner improvements for multiplatform projects New type inference Perfor…

We are happy to announce the 0.8.2 release of Kotlin/Native. In addition to the bug fixes and improvements, we have introduced support for Kotlin/Native Gradle projects directly in CLion! (more…)…

TeamCity uses Service Messages to provide an easy API to allow for build scripts integration, i.e. the build providing status reports, artifacts publishing, test reporting, etc. A Service Message has the following format: ##teamcit Service Messages introduce a communication protocol for data exc…

Today I'd like to share with you a plugin for TeamCity 6.5 that provides support for NuGet, the open source developer focused package management system for the .NET platform. What does the plugin bring? NuGet Packages Installer The plugin adds dedicated build runner that allows you to: Install NuG…

As we promised, we continue the configuration parameters story started in the previous post. Today, I'd like to tell you about .NET related properties. TeamCity .NET plugins provide a bunch of predefined properties indicating that .NET Framework/SDK/Visual Studio/Mono are detected on build agent. Pr…

After our posts about TeamCity's new multiple build steps (previously called "multiple build runners") feature and further changes in .NET build runners, I believe that plugin developers might have some questions to be clarified. So today, I'm going to shed some light on the major agent-side API c…

Have you already tried multiple runners in latest TeamCity 6.0 EAP builds? If you have, there's no need to repeat that now you can split the build procedure into steps and add as many build runners to be invoked sequentially as you need, for instance, call a NAnt script before compiling VS solutions…