GitLab CI vs TeamCity

Overview

TeamCity

Stacks1.2K

Followers1.1K

Votes316

GitLab CI

Stacks2.3K

Followers1.6K

Votes75

GitHub Stars0

Forks0

GitLab CI vs TeamCity: What are the differences?

Introduction

GitLab CI and TeamCity are both popular continuous integration (CI) tools that automate the process of building, testing, and deploying applications. While they share some similarities, there are several key differences between the two.

Deployment Flexibility: GitLab CI provides built-in deployment capabilities, allowing you to deploy your application to various environments directly from your CI pipeline. In contrast, TeamCity does not have native deployment features and requires additional plugins or custom scripts to achieve the same level of deployment flexibility.
Hosted vs. Self-hosted: GitLab CI is part of the GitLab platform, which offers a hosted solution where all components, including the CI/CD, are bundled together. On the other hand, TeamCity is a self-hosted tool that needs to be set up and managed on your own infrastructure or servers.
Built-in Code Review: GitLab CI tightly integrates with its code repository, providing built-in code review features. Developers can request code reviews directly within the GitLab platform, allowing for a streamlined and collaborative review process. TeamCity, being primarily a CI tool, does not have this native code review functionality and relies on external code review tools.
Extensibility and Plugin Ecosystem: TeamCity has a vast ecosystem of plugins that can be leveraged to extend its capabilities and integrate with various tools and technologies. It supports a wide range of integrations out of the box and has a mature plugin development ecosystem. GitLab CI, while also extensible, has a relatively smaller plugin ecosystem compared to TeamCity.
Built-in Container Registry: GitLab CI provides a built-in container registry, enabling you to conveniently store and manage Docker images for your applications. This integration simplifies the process of building and deploying containerized applications. TeamCity does not have a built-in container registry and relies on external solutions for managing Docker images.
Pricing Model: GitLab CI is part of the GitLab platform, which offers a range of pricing options, including a free version. The pricing for GitLab is based on user seats and additional features. TeamCity, on the other hand, has a license-based pricing model, where you need to purchase licenses based on the number of build agents and users.

In summary, GitLab CI offers a more integrated solution with built-in deployment capabilities and code review features. It also includes a built-in container registry and provides flexible pricing options. TeamCity, on the other hand, has a robust plugin ecosystem and allows for self-hosting, making it a popular choice for organizations that require extensive customization and control over their CI infrastructure.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on TeamCity, GitLab CI

Stratos

Jan 13, 2020

Needs advice

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

Fast SBT builds (caching)
Low maintenance overhead (ideally serverless)
Everything as code

Ease of use

181k views181k

Comments

Anonymous

Feb 14, 2020

Decided

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like:

Add repo
Click - Click - Click
You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

157k views157k

Comments

Detailed Comparison

TeamCity	GitLab CI
TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.	GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface; Simplified setup: create projects from just a VCS repository URL;Run multiple builds and tests under different configurations and platforms simultaneously; Make sure your team sustains an uninterrupted workflow with the help of Pretested commits and Personal builds; Have build history insight with customizable statistics on build duration, success rate, code quality, and custom metrics; Enable cost-effective on-demand build infrastructure scaling thanks to tight integration with Amazon EC2; Easily extend TeamCity functionality and add new integrations using Java API; Great visual project representation. Track any changes made by any user in the system, filter projects and choose style of visual change status representation;	-
Statistics
GitHub Stars -	GitHub Stars 0
GitHub Forks -	GitHub Forks 0
Stacks 1.2K	Stacks 2.3K
Followers 1.1K	Followers 1.6K
Votes 316	Votes 75
Pros & Cons
Pros 61 Easy to configure 37 Reliable and high-quality 32 On premise 32 User friendly 32 Github integration Cons 3 High costs for more than three build agents 2 Proprietary 2 User-friendly 2 User friendly	Pros 22 Robust CI with awesome Docker support 13 Simple configuration 9 All in one solution 7 Source Control and CI in one place 5 Free and open source Cons 2 Works best with GitLab repositories
Integrations
Slack	GitLab

What are some alternatives to TeamCity, GitLab CI?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Related Comparisons

GitLab CI vs TeamCity: What are the differences?

Introduction

Deployment Flexibility: GitLab CI provides built-in deployment capabilities, allowing you to deploy your application to various environments directly from your CI pipeline. In contrast, TeamCity does not have native deployment features and requires additional plugins or custom scripts to achieve the same level of deployment flexibility.
Hosted vs. Self-hosted: GitLab CI is part of the GitLab platform, which offers a hosted solution where all components, including the CI/CD, are bundled together. On the other hand, TeamCity is a self-hosted tool that needs to be set up and managed on your own infrastructure or servers.
Built-in Code Review: GitLab CI tightly integrates with its code repository, providing built-in code review features. Developers can request code reviews directly within the GitLab platform, allowing for a streamlined and collaborative review process. TeamCity, being primarily a CI tool, does not have this native code review functionality and relies on external code review tools.
Extensibility and Plugin Ecosystem: TeamCity has a vast ecosystem of plugins that can be leveraged to extend its capabilities and integrate with various tools and technologies. It supports a wide range of integrations out of the box and has a mature plugin development ecosystem. GitLab CI, while also extensible, has a relatively smaller plugin ecosystem compared to TeamCity.
Built-in Container Registry: GitLab CI provides a built-in container registry, enabling you to conveniently store and manage Docker images for your applications. This integration simplifies the process of building and deploying containerized applications. TeamCity does not have a built-in container registry and relies on external solutions for managing Docker images.
Pricing Model: GitLab CI is part of the GitLab platform, which offers a range of pricing options, including a free version. The pricing for GitLab is based on user seats and additional features. TeamCity, on the other hand, has a license-based pricing model, where you need to purchase licenses based on the number of build agents and users.

GitLab CI vs TeamCity

Overview