GitLab CI聽vs聽TeamCity

Need advice about which tool to choose?Ask the StackShare community!

GitLab CI

2.2K
1.5K
+ 1
75
TeamCity

1.2K
1K
+ 1
309
Add tool

GitLab CI vs TeamCity: What are the differences?

GitLab CI: GitLab integrated CI to test, build and deploy your code. 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; TeamCity: TeamCity is an ultimate Continuous Integration tool for professionals. 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 CI and TeamCity can be primarily classified as "Continuous Integration" tools.

"Robust CI with awesome Docker support" is the top reason why over 16 developers like GitLab CI, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.

According to the StackShare community, GitLab CI has a broader approval, being mentioned in 206 company stacks & 90 developers stacks; compared to TeamCity, which is listed in 168 company stacks and 51 developer stacks.

Advice on GitLab CI and TeamCity
Needs advice
on
CircleCICircleCIGitLab CIGitLab CI
and
Jenkins XJenkins X

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
See more
Replies (3)
Glenn Gillen
Recommends
BuildkiteBuildkite

I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:

Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.

It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.

And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though 馃槥) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.

See more
Recommends
jFrogjFrog

I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.

See more
Estu Fardani
Recommends
GitLab CIGitLab CI

more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation

Weakness: * Need use gitlab as repository to bring more powerful configuration

See more
Decisions about GitLab CI and TeamCity

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: 1. Add repo 2. Click - Click - Click 3. 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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of GitLab CI
Pros of TeamCity
  • 22
    Robust CI with awesome Docker support
  • 13
    Simple configuration
  • 9
    All in one solution
  • 7
    Source Control and CI in one place
  • 5
    Integrated with VCS on commit
  • 5
    Free and open source
  • 5
    Easy to configure own build server i.e. GitLab-Runner
  • 2
    Hosted internally
  • 1
    Built-in Docker Registry
  • 1
    Built-in support of Review Apps
  • 1
    Pipeline could be started manually
  • 1
    Enable or disable pipeline by using env variables
  • 1
    Gitlab templates could be shared across logical group
  • 1
    Easy to setup the dedicated runner to particular job
  • 1
    Built-in support of Kubernetes
  • 60
    Easy to configure
  • 37
    Reliable and high-quality
  • 31
    User friendly
  • 31
    Github integration
  • 31
    On premise
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 4
    REST API
  • 4
    Great support by jetbrains
  • 4
    Projects hierarchy
  • 4
    Chain dependencies
  • 4
    Fully-functional out of the box
  • 3
    100+ plugins
  • 3
    Free for small teams
  • 3
    Build templates
  • 3
    Per-project permissions
  • 3
    Personal notifications
  • 2
    Upload build artifacts
  • 2
    Ide plugins
  • 2
    Artifact dependencies
  • 2
    Official reliable support
  • 2
    GitLab integration
  • 2
    Build progress messages promoting from running process
  • 2
    Smart build failure analysis and tracking
  • 1
    Powerful build chains / pipelines
  • 1
    Repository-stored, full settings dsl with ide support
  • 1
    TeamCity Professional is FREE
  • 1
    Built-in artifacts repository
  • 0
    1
  • 0
    Hosted internally
  • 0
    High-Availability

Sign up to add or upvote prosMake informed product decisions

Cons of GitLab CI
Cons of TeamCity
  • 2
    Works best with GitLab repositories
  • 2
    User-friendly
  • 2
    User friendly
  • 1
    Proprietary
  • 1
    High costs for more than three build agents

Sign up to add or upvote consMake informed product decisions