Jenkins vs TeamCity

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

Jenkins

38.8K
31.5K
+ 1
2.2K
TeamCity

896
852
+ 1
306
Add tool

Jenkins vs TeamCity: What are the differences?

Both Jenkins and TeamCity are continuous integration tools that serve many of the same purposes. Jenkins is an open source tool, while TeamCity is a proprietary offering from JetBrains. Jenkins is older than TeamCity, so it has a larger community and wider use in general; it appears in far more stacks than its competitor. TeamCity is considered by users to be easier to configure and more straightforward to use, while Jenkins is appreciated for its rich set of plugins and integrations.

Advice on Jenkins and TeamCity
Needs advice
on
Jenkins
and
Azure Pipelines

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

See more
Replies (1)
Recommends
GitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Axceligent Solutions · | 3 upvotes · 152.3K views
Needs advice
on
Jenkins
and
GoCD

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 140.5K views

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
Jenkins
and
Concourse

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 60.5K views
Recommends
Concourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Decisions about Jenkins and TeamCity
Pedro Gil Carvalho
Head of Engineering at Lengoo GmbH · | 4 upvotes · 3.6K views

We replaced Jenkins with Github Actions for all our repositories hosted on Github. GA has two significant benefits for us compared to an external build tool: it's simpler, and it sits at eye level.

Its simplicity and smooth user experience makes it easier for all developers to adopt, giving them more autonomy.

Sitting at eye level means it's completely run and configured right alongside the code, so that it's easier to observe and adjust our builds as we go.

These two benefits have made "the build" less of a system engineer responsibility and more of a developer tool, giving developers more ownership from code to release.

See more
Kirill Mikhailov

Jenkins is a friend of mine. 😀

There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.

See more
Stephen Badger | Vital Beats
Senior DevOps Engineer at Vital Beats · | 2 upvotes · 59.6K views

Within our deployment pipeline, we have a need to deploy to multiple customer environments, and manage secrets specifically in a way that integrates well with AWS, Kubernetes Secrets, Terraform and our pipelines ourselves.

Jenkins offered us the ability to choose one of a number of credentials/secrets management approaches, and models secrets as a more dynamic concept that GitHub Actions provided.

Additionally, we are operating Jenkins within our development Kubernetes cluster as a kind of system-wide orchestrator, allowing us to use Kubernetes pods as build agents, avoiding the ongoing direct costs associated with GitHub Actions minutes / per-user pricing. Obviously as a consequence we take on the indirect costs of maintain Jenkins itself, patching it, upgrading etc. However our experience with managing Jenkins via Kubernetes and declarative Jenkins configuration has led us to believe that this cost is small, particularly as the majority of actual building and testing is handled inside docker containers and Kubernetes, alleviating the need for less supported plugins that may make Jenkins administration more difficult.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Jenkins
Pros of TeamCity
  • 521
    Hosted internally
  • 463
    Free open source
  • 313
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 208
    Rich set of plugins with good documentation
  • 108
    Has support for build pipelines
  • 72
    Open source and tons of integrations
  • 63
    Easy setup
  • 61
    It is open-source
  • 54
    Workflow plugin
  • 11
    Configuration as code
  • 10
    Very powerful tool
  • 9
    Many Plugins
  • 8
    Great flexibility
  • 8
    Git and Maven integration is better
  • 7
    Continuous Integration
  • 6
    Slack Integration (plugin)
  • 6
    Github integration
  • 5
    100% free and open source
  • 5
    Self-hosted GitLab Integration (plugin)
  • 5
    Easy customisation
  • 4
    Docker support
  • 3
    Platform idnependency
  • 3
    Pipeline API
  • 3
    Fast builds
  • 3
    Excellent docker integration
  • 2
    Hosted Externally
  • 2
    It`w worked
  • 2
    Can be run as a Docker container
  • 2
    Customizable
  • 2
    AWS Integration
  • 2
    It's Everywhere
  • 2
    JOBDSL
  • 1
    NodeJS Support
  • 1
    PHP Support
  • 1
    Ruby/Rails Support
  • 1
    Universal controller
  • 1
    Easily extendable with seamless integration
  • 1
    Build PR Branch Only
  • 59
    Easy to configure
  • 37
    Reliable and high-quality
  • 31
    User friendly
  • 31
    On premise
  • 31
    Github integration
  • 18
    Great UI
  • 16
    Smart
  • 12
    Can run jobs in parallel
  • 12
    Free for open source
  • 8
    Crossplatform
  • 4
    Fully-functional out of the box
  • 4
    Projects hierarchy
  • 4
    Chain dependencies
  • 4
    REST API
  • 4
    Great support by jetbrains
  • 3
    Free for small teams
  • 3
    Personal notifications
  • 3
    Per-project permissions
  • 3
    Build templates
  • 3
    100+ plugins
  • 2
    Upload build artifacts
  • 2
    Build progress messages promoting from running process
  • 2
    Artifact dependencies
  • 2
    Smart build failure analysis and tracking
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 1
    Repository-stored, full settings dsl with ide support
  • 1
    Built-in artifacts repository
  • 1
    Powerful build chains / pipelines
  • 1
    TeamCity Professional is FREE
  • 0
    Official reliable support
  • 0
    High-Availability
  • 0
    Hosted internally

Sign up to add or upvote prosMake informed product decisions

Cons of Jenkins
Cons of TeamCity
  • 12
    Workarounds needed for basic requirements
  • 8
    Groovy with cumbersome syntax
  • 6
    Plugins compatibility issues
  • 6
    Limited abilities with declarative pipelines
  • 5
    Lack of support
  • 4
    No YAML syntax
  • 2
    Too tied to plugins versions
  • 1
    Proprietary
  • 1
    High costs for more than three build agents
  • 1
    User friendly
  • 1
    User-friendly

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is 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.

What is TeamCity?

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.

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

Why do developers choose TeamCity vs Jenkins?

  • TeamCity users site its easy configurability, reliability, and great UI as factors in choosing it over other options.
  • Users of Jenkins laud it for being open source, a deciding factor for many developers. In addition they list its plugin and integration ecosystem as pros.
What companies use Jenkins?
What companies use TeamCity?
See which teams inside your own company are using Jenkins or TeamCity.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Jenkins?
What tools integrate with TeamCity?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Mar 24 2021 at 12:57PM

Pinterest

+7
3
1175
+4
4
1661
Dec 4 2019 at 8:01PM

Pinterest

+4
5
2885
+22
17
13185
What are some alternatives to Jenkins and TeamCity?
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.
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.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
Apache Maven
Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
Puppet Labs
Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
See all alternatives
How developers use Jenkins and TeamCity
DigitalPermits uses
TeamCity

TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned.

Stack Exchange uses
TeamCity

TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:

  • Tell HAProxy to take the server out of rotation via a POST
  • Delay to let IIS finish current requests (~5 sec)
  • Stop the website (via the same PSSession for all the following)
  • Robocopy files
  • Start the website
  • Re-enable in HAProxy via another POST
Kalibrr uses
Jenkins

All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.

Wirkn Inc. uses
Jenkins

Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.

Bùi Thanh uses
Jenkins
  • Continuous Deploy
  • Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
  • Staging and production stages: Build and rollback quicly with Ansistrano playbook
  • Sending messages of job results to Chatwork.
AngeloR uses
Jenkins

Currently serves as the location that our QA team builds various automated testing jobs.

At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.

Trusted Shops GmbH uses
Jenkins

We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.

Sascha Manns uses
TeamCity

I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.

Andrew King uses
TeamCity

Continuous integration for iOS apps.

One Legal uses
TeamCity

Build system.