How-To's

Today we are wrapping up our .NET integration demo. In this series, we've been explaining how TeamCity can integrate with .NET and walking you through a tutorial. To catch up with the demo, read the previous posts: Part 1: New approach and demo Part 2: Testing and building projects This project has already been built on the demo TeamCity server. You can sign in as a guest and explore the build results. Or, fork the source repo and build the project yourself. After we tested and built our applications for different platforms, we can finally pack and deploy them! Creating NuGet packages The &q

TeamCity REST API is a powerful tool which lets you integrate external applications with the TeamCity server and create diverse script interactions. To make this instrument more useful and easier to understand, we have reworked the REST API documentation. Compared to a general guide we had in the past, the new documentation provides more details and offers better navigation between sections. For beginners, it offers a quick start guide and describes common use cases. We plan to describe more popular cases and explore advanced topics in the future. Experienced users will appreciate the full re

In this blog series, we talk about the new approach we use to integrate TeamCity with .NET. Part 1 describes the .NET runner, that covers most of the core integration functionality, and introduces a demo project. In Part 2, we will dig deeper into the demo project and explore its Test and Build configurations. Source repo: https://github.com/JetBrains/teamcity-dotnet-samples This project has already been built on the demo TeamCity server. You can sign in as a guest and explore the build results. To run all build configurations, we use the following agents: (A) Windows 10 x64 Pro 10.0.19041 V

This post was created in collaboration with a TeamCity .NET developer Nikolay Pianikov. Microsoft has recently released .NET 5, a new SDK that unifies all the 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. In this blog series, we'll tell you about this new integration and take you through a demo project you can run on your server. Old approach vs. new approach If you've worked with .NET in TeamCity before, you'll already know that the variety of integration tools it provides can be pr

This post has been created in collaboration with LambdaTest. In this post, we will show how to set up TestNG tests in TeamCity and power them up with the LambdaTest signature Selenium Grid Cloud functionality. LambdaTest allows executing automated tests on over 2000+ browsers. This helps achieve quicker continuous integration and more stable delivery of products to consumers. With its interactive UI dashboard, you get detailed test reports, logs, and videos, which makes it easier to analyze and debug any product issues. You can read more about the benefits of the TeamCity integration with La

In version 2019.2, TeamCity introduced the ability to use context parameters in Kotlin DSL project configurations. These parameters can vary from project to project in TeamCity while the common project declaration stays the same. It means that you can create one DSL project template and reuse it in as many projects on the TeamCity server as necessary. This is far more convenient than storing similar DSL specifications in multiple branches or creating a complex project hierarchy in TeamCity. In this video, we’ll explore an example project and show you how to utilize the power of context paramet

In TeamCity 2020.1, we have introduced a highly demanded feature – conditional build steps. With new execution conditions, you can control whether or not a given build step is executed in every build run, depending on the current environment and parameters. In this video demonstration we: explain how to add an execution condition to a step; show how to elevate your building experience by creating custom conditions based on build parameters. Here is a quick recap of the video: Adding execution conditions To add execution conditions to a build step: Open the step's advan

In TeamCity, when we need to build something, we create a build configuration. A build configuration consists of the build steps and is executed in one run on the build agent. You can define as many build steps as you like in one build configuration. However, if the number of steps grows too large, it makes sense to examine what the build configuration is doing – maybe it does too many things! We can split the steps into multiple build configurations and use TeamCity snapshot dependencies to link the configurations into a build chain. The way TeamCity works with build chains enables quite a f