Overview

Travis CI

Stacks26.5K

Followers6.7K

Votes1.7K

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

TeamCity

Stacks1.1K

Followers1.1K

Votes316

Jenkins vs TeamCity vs Travis CI: What are the differences?

Introduction:

When it comes to CI/CD tools, Jenkins, TeamCity, and Travis CI are popular choices for automating software development processes. Each tool has its own set of features and advantages, making them suitable for different use cases.

Architecture: Jenkins is an open-source automation server with a vast plugin ecosystem that supports various integrations and customizations. TeamCity, on the other hand, is a proprietary CI/CD tool developed by JetBrains that offers a more streamlined user interface and easy setup for smaller teams. Travis CI is a cloud-based CI service that focuses on simplicity and quick setup for GitHub projects.
Scalability: Jenkins can be scaled horizontally to handle multiple build agents and pipelines, making it suitable for large enterprises with complex build requirements. TeamCity provides better out-of-the-box scalability features, such as build chains and build configurations, making it easier to manage and scale CI/CD workflows. Meanwhile, Travis CI offers a more simplified approach to scaling with limited customization options compared to Jenkins and TeamCity.
Integration: Jenkins offers extensive integration capabilities through its vast plugin ecosystem, enabling users to connect with various tools and services seamlessly. TeamCity provides built-in integrations with popular version control systems and IDEs, streamlining the setup process for developers. Travis CI focuses on tight integration with GitHub repositories, making it a preferred choice for projects hosted on the platform.
Pricing: Jenkins is a free and open-source tool, making it a cost-effective option for organizations with budget constraints. TeamCity comes with a licensing fee based on the number of build agents, making it more suitable for teams willing to invest in a comprehensive CI/CD solution. Travis CI offers a free tier for open-source projects but charges for private repositories and additional build concurrency.
Customization: Jenkins allows extensive customization through its plugin ecosystem and scriptable pipeline definitions, giving users full control over their CI/CD workflows. TeamCity offers a more opinionated approach with predefined build steps and templates, making it easier for beginners to set up their pipelines. Travis CI provides a straightforward configuration process through its YAML-based configuration file, offering a balance between flexibility and simplicity.
Community Support: Jenkins has a large and active community that contributes plugins, documentation, and support resources, making it easier for users to troubleshoot issues and extend the platform's functionality. TeamCity has a smaller but dedicated user base, with official support from JetBrains ensuring prompt assistance and updates. Travis CI benefits from GitHub's community, with a focus on user-friendly documentation and seamless GitHub integration for easy adoption.

In Summary, Jenkins, TeamCity, and Travis CI offer distinct features in terms of architecture, scalability, integration, pricing, customization, and community support, catering to different requirements and preferences in the CI/CD landscape.

Advice on Travis CI, Jenkins, TeamCity

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

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.

663k views663k

Comments

A

Engineering Team Lead at DCMN GmbH

Oct 22, 2021

Decided

Github Actions allowed us to drop previous CI/CD technologies like Jenkins or AWS CodeBuild. The main advantages for us are: - The Infrastructure-as-Code approach of Github Actions enables us to keep CI/CD configurations next to the code. - Github as a single platform for repositories and CI/CD simplifies our stack and effort to manage it on the daily basis.

TVcloud Team <3 Github Actions

72.2k views72.2k

Comments

Pedro Gil

Head of Engineering at lengoo GmbH

May 4, 2021

Decided

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.

77.6k views77.6k

Comments

Detailed Comparison

Travis CI	Jenkins	TeamCity
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.	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.	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.
Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.;Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.;Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.	Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support	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 24.6K	GitHub Stars -
GitHub Forks -	GitHub Forks 9.2K	GitHub Forks -
Stacks 26.5K	Stacks 59.2K	Stacks 1.1K
Followers 6.7K	Followers 50.4K	Followers 1.1K
Votes 1.7K	Votes 2.2K	Votes 316
Pros & Cons
Pros 506 Github integration 388 Free for open source 271 Easy to get started 191 Nice interface 162 Automatic deployment Cons 8 Can't be hosted insternally 3 Unstable 3 Feature lacking 2 Incomplete documentation for all platforms	Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Limited abilities with declarative pipelines 7 Lack of support	Pros 61 Easy to configure 37 Reliable and high-quality 32 User friendly 32 On premise 32 Github integration Cons 3 High costs for more than three build agents 2 User-friendly 2 User friendly 2 Proprietary
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	No integrations available	Slack

What are some alternatives to Travis CI, Jenkins, TeamCity?

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.

Appveyor

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.