build runner

The recently released TeamCity 2021.2 introduces a new build runner — C# Script. We’ve created it for users who want to automate their routine CI/CD operations using the familiar syntax of C# and all its scripting conveniences. TL;DR: The runner’s main advantages are:- It’s tightly integrated with TeamCity and supports all its handy features like a detailed build log and parameterized build properties.- It’s platform-independent and can run inside a Docker container.- It can automatically restore NuGet packages mentioned in your scripts.- It can access public, private, and TeamCity-internal

The recording of our April 30 webinar, Getting Started with TeamCity Plugins is now available on the JetBrains YouTube channel. In this webinar, we developed a custom runner plugin for TeamCity. The plugin adds a new build step for the echo command and displays the result of the execution in a custom tab for the completed build. You can find the source code of the plugin on GitHub. The timeline: 4:23 - Generate project with Maven archetype 8:23 - Create server-side part of the plugin 18:31 - Create agent-side part of the plugin 24:47 - Configure TeamCity SDK Maven plugin 31:13 - Adding co

Deploying ASP.NET applications can be done in a multitude of ways. Some build the application on a workstation and then xcopy it over to the target server. Some use a build server, download the artifacts, change the configuration files and xcopy those over to the server. The issue with that is something bad creeps in: deployments become unpredictable. Using the premise of Continuous Delivery, we can make deployments predictable. Automating all the steps will ensure that deployments can always be done and reproduced, ideally by going through a pipeline of environments. TeamCity may ha

When working with NuGet we can make use of package restore. The concept is simple: instead of committing packages that we depend on to source control, we only commit the list of dependencies we need and download the assemblies during build. In TeamCity, package restore is supported in various ways. We can use the NuGet.targets file (NuGet v2.6 and earlier) or run nuget restore from the command line (v2.7). TeamCity has a build runner which makes setting up package restore a breeze: the NuGet Installer. NuGet Installer The NuGet Installer build runner will make sure all package dependencie

TeamCity comes with a series of Runners out of the box which offer support for different functionalities such as MSBuild, Ant, Code Inspections, Gradle support, etc. In addition to these, there are a variety of runners that are supported via plugins, from FTP uploads to Grails and other things. What happens when you want to perform some operation that is not supported via a runner? We could use the Command Line runner or build or own plugin. Each have their own benefits and disadvantages. The first one is quite straightforward, but the second offers more flexibility and a better user experi

A while ago we blogged about using TeamCity to do Continuous Integration for PHP. TeamCity developers never seem to sleep: with TeamCity 8 a new feature called meta-runners was introduced. Meta runners allow us to reuse build steps by representing them as a native TeamCity runner. In other words, they allow us to make several build steps easier. Which is exactly what we decided to do: create some meta runners based on our previous blog post and make it really easy to run several PHP-related build steps. The Meta-runner Power Pack for TeamCity 8 contains a set of PHP-related meta runners:

Over the last few weeks we have made a great deal of improvements in .NET inspections support. As a result .NET Inspections (powered by JetBrains ReSharper) and FxCop inspections runners produce much more clear results. In case you missed, some time ago we announced new .NET inspections runner based on ReSharper inspections engine, and we already received feedback on it. Thanks to our EAP users we were able to fix a number of serious problems: - LINQ usages are marked as unresolved symbols; - TW-18724 NUnit attributes usages (and all External Annotations); - TW-18730 Usages of resources in WP

"I see dead code" - .NET developers all over the world know this slogan due to incredible code analysis feature provided by JetBrains ReSharper. One of the most wanted TeamCity features was to have .NET inspections results right on build server. Starting with the latest EAP you have it! The only thing you need to do to get all the benefits of ReSharper's analysis right in TeamCity is to add Inspections (.NET) build runner as a build step to your build configuration. Configuration is quite easy, so let's just take a look at how the results look when this runner is configured - you can find

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 changes that we've made to support multiple build steps. I hope this post will help you to painlessly improve your build runner plugins. AgentRunningBuild interface no longer represents parameters for a build runner. We've introduced new interface BuildRunnerContext that provides parameters for buil

It's about time to try a new TeamCity 6.0 EAP build, which introduces the long-awaited feature - Multiple Build Runners. Many of you voted for this one, and now we would like to hear your feedback on it. Here's how it works - you can add as many build runners to a single build configuration as you need, and they will be executed step by step. In the end, the build gets merged status and the output goes into the same build log. If some step fails, the rest are not executed. We're still actively develop this feature, so it's up to you to help us make it better! In addition to Multiple Build Ru