plugin

Bazel is an interesting build tool for compiling large projects and it comes with build-ins for Java, C++, Python, etc. Some of our users are adopting Bazel and we received a few requests to support it in TeamCity. Bazel plugin for TeamCity is now published in the plugin repository and could be installed as an additional TeamCity plugin. The plugin provides Bazel command build runner and integrates with the core functionality of TeamCity. Bazel build step configuration You will be able to see Bazel’s command output in the structured build log. The plugin also assists in capturing the

The hassle with Pull Requests These days pull requests is a common technique of accepting changes from third-party contributors. In fact, it proved to be so convenient that some companies started to use it even for their regular development workflows. It is possible to configure TeamCity to run builds on GitHub pull request branches. One had to provide a VCS root branch specification like refs/pull/*/head for that. However, this configuration is not without its downsides. For instance, with this configuration, the pull request for TeamCity is just a branch in a Git repository. It means that

We are happy to announce that now TeamCity provides a tight integration with Google Cloud services. The Google Cloud Agents plugin allows using Google Compute Engine to start cloud instances on demand to scale the pool of cloud build agents and also supports using cost-efficient preemptible virtual machines. The Google Artifact Storage plugin provides the ability to use Google Cloud Storage to keep external build artifacts. Installation To enable these TeamCity integrations with the Google Cloud, you need to download the Google Cloud Agents and Google Artifact Storage from the plugins galler

The .NET Core development platform is the next wave of .NET ecosystem evolution which brings cross-platform targets for your existing or new products. Microsoft ships .NET Core SDK packages with a runtime for supported platforms and command line tools (.NET CLI) to build, test, and pack such projects. The .NET Core support plugin for TeamCity aims to bring streamline support for .NET Core CLI by providing .NET Core build steps, CLI detection on the build agents, and auto-discovery of build steps in your repository. Installation The plugin is available for download from the TeamCity plugin

Microsoft has recently introduced a new way to deploy cloud resources, so currently there exist two Azure deployment models supported by TeamCity as two separate plugins. The earlier Azure deployment model is in the feature freeze state and is now called Azure Classic. The same goes for the existing TeamCity Azure support, now called TeamCity Azure Classic plugin. Azure Resource Manager is the new Azure deployment model, which has some advanced features and is now becoming popular. More and more users want to deploy cloud agents with it, so today we are glad to announce a new plugin, the

In a large TeamCity setup with many projects, it's often very difficult to predict the load on build agents, for example during releases. One minute we need only one agent to be running, the next minute we need 50. Not to worry! TeamCity supports scaling out builds to Amazon EC2, and starting today, also Microsoft Azure! For each queued build, TeamCity first tries to start it on one of the regular, non-cloud agents. If there are no regular agents available, TeamCity finds a virtual machine or virtual machine image with a compatible agent and starts it on Azure. TeamCity ensures that the con

Today we have some interesting news for you - the Torrent plugin for TeamCity! With this plugin, users and build agents can download TeamCity build artifacts faster, especially in a distributed environment. A bit of the BitTorrent protocol details For those of you who are not familiar with BitTorrent - this is a peer-to-peer protocol. It means there is no single server for shared files. Instead, the files can be downloaded from peers that already have these files or parts of them. Still, a server is required to find peers. This server is called a torrent tracker. To download a file, a

This post describes one of the new features in the upcoming TeamCity 8.0 Using TeamCity, we can easily set up a build farm using a central TeamCity server and several connected build agents. By having multiple build agents, we can run builds and build configurations in parallel. Different branches of the same project can build simultaneously on different build agents,  personal builds can be run on one build agent while the nightly build is running on another agent and so on. But what if we have multiple build agents and we want to constrain parallelism for some projects? What if we do want t

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