Jenkins to TeamCity Migration Guidelines
This document provides the basics you need to know when migrating from Jenkins to a TeamCity CI server. TeamCity is quite different from Jenkins in terms of concepts related to managing CI and CD. To learn more about Continuous Delivery and get tips on building a production pipeline, follow our CI/CD Guide. If you want to jump in and get started with TeamCity right away, see the Getting Started instructions.
Jenkins and TeamCity mostly feature the same set of concepts, however, with slightly different naming. The following table provides a mapping for some of the Jenkins concepts to the TeamCity counterparts.
Dumb Slave / Permanent Agent
View or Folder
Build Steps (partially)
Build Steps (partially)
Source Control Management (SCM)
Build Chain (via snapshot dependencies)
Migrating Freestyle project
A Freestyle project is the most common project type in Jenkins so we describe the TeamCity counterparts for a Freestyle project to guide the migration.
Project and Build Configuration
There are some conceptual differences in how the build jobs are configured in Jenkins and TeamCity.
Build Configuration is the TeamCitys counterpart of Jenkins Job/Item/Project. However, a Build Configuration requires a Project instance to be created first. In fact, the notion of Project in TeamCity is the first big difference that a user encounters when migrating from Jenkins. The Project contains a good portion of settings required for the build configurations. All settings that are assigned to a Project in TeamCity are listed here.
Source Code Management (SCM) of a Jenkins build job corresponds to a VCS root in Project Settings in TeamCity. A Project may include an arbitrary number of VCS Roots. Any Build Configuration may use any number of VCS Roots of the Project.
When only a part of the VCS Root is required, it is possible to use VCS Checkout Rules. This allows mapping the directories from the configured VCS Root to subdirectories in the build checkout directory on a Build Agent.
The Build Environment section of the Freestyle project in Jenkins specifies additional features for the project. In TeamCity, the corresponding features may be configured in various sections, depending on the goal: general project settings, build configuration settings, VCS root settings, and so on.
To clean the workspace before the build, enable the Clean build checkbox in Version Control Settings of a Build Configuration.
Environment variables can be accessed by specifying a special
%env.<environment variable name>%pattern (example:
%env.JAVA_HOME%) in various places of the configuration.
A Freestyle project allows configuring optional triggers to control when Jenkins will start the builds. In most cases, a trigger in a Jenkins project will be a counterpart in TeamCity.
A number of options for triggering builds in TeamCity are available. It is possible to watch for changes in a source control repository, monitor an external resource, or even a Maven dependency. It is possible to schedule builds periodically, besides, the REST API is available to trigger builds externally.
This is where the real work happens. This part is mostly identical in Jenkins and TeamCity. TeamCity provides a large number of build runners out of the box. You can configure several build steps to run the required tasks for the given Build Configuration.
Building Maven project
A Jenkins Maven project doesnt have a direct counterpart in TeamCity. Instead, an appropriate build step is selected to perform the work. In fact, TeamCity automates a lot of the setup for Maven projects and provides an additional build triggering option based on dependencies.
Post-build Actions of the Freestyle project can be mapped either to the specific attributes of a Project/Build Configuration in TeamCity or by using an additional build step. You may also find a relevant solution to the task by adding Build features to the Build Configuration in TeamCity.
An individual build step may be configured to execute depending on the success or failure of the previous build step(s) of the same Build Configuration.
Working with branches
TeamCity provides support for the Feature Branches in distributed version control systems (DVCS).
The support for Feature Branches integrates with the various TeamCity functions. For instance, the Branch Remote Run Trigger automatically starts a new personal build each time TeamCity detects changes in particular branches of the VCS roots of the build configuration.
Heres a list of some of the highlights related to Feature Branches in TeamCity:
The build branch name can be specified in an artifact dependency
The VCS, Schedule, and Finish build triggers support the branch filter setting
VCS labeling also supports the branch filter
Mercurial bookmarks can be used in the branch specification, so, if you prefer to use bookmarks instead of standard Mercurial branches, you can fully use the TeamCity feature branches with them
Git tags can be used in the branch specification. Some teams use Git tags the same way as branches, i.e., once a new tag is set, a build should be started in TeamCity in a branch designated by the tag name.
TeamCity comes with a lot of features built-in by default, and can be further extended by installing additional plugins.
A build pipeline in TeamCity is called a Build Chain. It is a set of Build Configurations connected via snapshot dependencies. The TeamCity Take on Build Pipelines article describes in detail how TeamCity handles build chains and what the implications are.
In Jenkins, to offload the master node, a permanent agent is configured to run builds.
TeamCity server doesnt run any builds itself. Instead, it always delegates the job to a build agent, which means in TeamCity builds are distributed by design.
The active agents count is visible at the top of the TeamCity server UI:
You can break the agents into separate groups called agent pools and assign those to the specific projects. In Build Configuration settings, it is possible to specify a number of Agent Requirements needed for the build.