It builds and publishes the console Clock app into a single executable under the bin/Clock.Console/linux-圆4 directory. NET 5.0 applications as well, so we can build and publish them using a single. Each configuration comprises two steps, one for each version of the app.Ĭlock.Console and Clock.Web are. Building console and web appsĪs is clear from their names, the 'Build console and web for win-圆4' and 'Build console and web for linux-圆4' configurations are responsible for building two versions of the app from two source subprojects: Clock.Console and Clock.Web. In the DSL, you can find both Linux and Windows test configurations under a common parent, TestBase. It is automatically installed from the package as an agent tool. To collect and analyze code coverage statistics, we’ve selected JetBrains dotCover. NET 5.0 application, so we can simply use the test command to run the tests. In the Windows configuration, the step looks similar but doesn’t use Docker. For example, in a Linux configuration, this step looks like this:įor Linux, the app’s libraries are tested inside the. These build configs, 'Test on Windows' and 'Test on Linux', test the app’s basic logic and collect code coverage statistics on Windows (agent A) and in a Linux Docker container.

To run all build configurations, we use the following agents:Īs described in Part 1, the demo project contains two build configurations that provide cross-platform testing of our app. You can sign in as a guest and explore the build results. This project has already been built on the demo TeamCity server. In Part 2, we will dig deeper into the demo project and explore its Test and Build configurations. NET runner, that covers most of the core integration functionality, and introduces a demo project. In this blog series, we talk about the new approach we use to integrate TeamCity with.

Jetbrains agent 2020