FYI

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

Some time ago we announced TeamCity Azure Resource Manager for TeamCity deployment in Azure cloud. Now we're glad to provide the TeamCity offer in the Azure Marketplace for streamlined TeamCity setup. It is also available as a TeamCity download option on the official JetBrains site: The offer lets you run a JetBrains TeamCity server and a local agent on an Azure Linux VM in Azure. Today we’ll go over a TeamCity instance setup on Azure, which will save you time and effort of configuration tasks. Prerequisites You’ll need an Azure subscription and about 10 minutes to set up TeamCi

Some time ago we announced the plugin that turns TeamCity into a torrent tracker and a seeder for large artifacts. Judging by the flow of feedback — both positive and not so much — the plugin is in use by quite a few of our users. To remedy the not-so-much part, we are presenting a new version of the plugin, BitTorrent Support, today. Plugin changes If you’re new to BitTorrent, you might want to read our previous post on the subject first. For those familiar with the plugin, here is the list of the critical performance and security bug fixes, as well as the new features: Optimized dow

We are happy to announce the Azure Resource Manager template for TeamCity. You can now deploy TeamCity to Azure cloud services and save time on configuration tasks. Get ready to start using TeamCity in several minutes! Deploy TeamCity to Azure Cloud Services The template performs the following tasks: Setting up of an external database Creating a virtual machine for the TeamCity server Configuring the TeamCity server machine Installing the TeamCity server Installing a TeamCity build agent Depending on your team size, you can select the appropriate TeamCity installation size

TeamCity has been able to run build agents on AWS EC2 instances for ages. In addition to this, the new plugin for TeamCity, Amazon ECS Support, allows running Docker-based build agents in an EC2 Container Service cluster. The plugin is compatible with TeamCity 2017.1.x and later. First, download the plugin and install it on the TeamCity server as usual. Next, create a cloud profile in your project Specify the AWS region and enter credentials to access AWS API and test your connection. To make the plugin work, the provided credentials need the IAM role with the following

Kubernetes nowadays is quite a popular way to run Docker containers. A number of teams and organizations already have a Kubernetes cluster configured and used in production. Now with the help of the TeamCity Kubernetes Support plugin, it is possible to use the same infrastructure to run TeamCity build agents. The plugin is compatible with TeamCity 2017.1.x and later. First, download the plugin and install it on the TeamCity server as usual. Then you can start by configuring a cloud profile in a project: Specify the URL of the Kubernetes API server (aka Kubernetes master), se

For a couple of weeks now, there has been a new button on the TeamCity website: Clicking it allows you to access TeamCity in the cloud, hosted by JetBrains. We call it TeamCity TestDrive. What is TestDrive? TestDrive is a limited cloud TeamCity offering. It is a way to try TeamCity for 60 days, without the need to download and install it. TestDrive is currently hosted on top of teamcity.jetbrains.com server, and lets users create one TeamCity project. It is free but it has some limitations with regards to the software that’s on the build agents. Why you should care Have you ever had a pro

As you might have noticed, there was recently an option added to the Get TeamCity page of our website: AWS. This lets you run TeamCity in AWS using the official CloudFormation template. In this post, we will go over what’s under the hood of the template, and why it may save you some time and effort. Usually, installing TeamCity on top of AWS is quite a time-consuming task. It requires the following steps: Setting up an external database, Configuring the EC2 instance to run a TeamCity server, Configuring it to then connect to the database, Installing the TeamCity server,

Starting from its very first version, TeamCity has provided support for IntelliJ platform-based IDEs. Because the IDEs are developed by JetBrains, this integration is the most powerful compared with other IDEs' integrations. The main idea behind the integration is the ability to take advantage of all the features provided by TeamCity as a continuous integration server without leaving the context of the IDE: using the integration, you can configure notifications, run builds and tests, get the build status, view your changes, assign investigations, and perform other actions available in TeamCit

When performing integration tests and deployments, build scripts need credentials to access external servers and services. Traditionally passwords are stored on the TeamCity server as secure parameters. But although secrets are masked in the UI, encrypted at rest, and protected from being exposed in the build log as plain text, this often does not provide a high enough level of security. HashiCorp Vault offers a unified approach to managing secrets and credentials, allows auditing access, and helps with password rotation. Integration with Vault Today we are presenting a new plugin to help bui

When building, testing, and deploying an application with TeamCity, you may need to run a build under a specific user account, different from the one used to run the build agent. TeamCity RunAs Plugin Overview The teamcity-runas plugin can be used to run TeamCity build steps under a specified user account on Windows or Linux. The plugin is compatible with TeamCity 10.0 and later. Installing Plugin System Administrators can download the runAs.zip from here and install it on the TeamCity server as usual. Configuring TeamCity Agents On Windows The teamcity-runas plugin requires the Team

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