CircleCI vs Jenkins vs Travis CI

CircleCI
CircleCI

3.1K
461
934
Jenkins
Jenkins

11.4K
2.9K
2K
Travis CI
Travis CI

4.1K
104
1.7K

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

CircleCI – A cloud-based tool that automates the integration and deployment process. Also focusses on testing every code change before it’s deployed, using methods such as unit tests, integrations tests, and functional tests. It integrates seamlessly with the current version control system.

Jenkins – A name to reckon in the CI market. Started by Sun’s engineers, and expanded into one of the most common open source CI tools. The CI tools help engineering teams automate their deployments. Automate your build, test, and deploy tasks. The tool supports Windows, Mac OSX and various Unix systems.

Travis CI – Created for open source projects, it is focused on the CI level, focused on improving the performance of the build process with automated testing and an alert system. Users can quickly test their code with Travis keeping track of changes and advising whether the change is successful or not.

- No public GitHub repository available -
- No public GitHub repository available -

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

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

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose CircleCI?
Why do developers choose Jenkins?
Why do developers choose Travis CI?
What are the cons of using CircleCI?
What are the cons of using Jenkins?
What are the cons of using Travis CI?
What companies use CircleCI?
What companies use Jenkins?
What companies use Travis CI?
What are some alternatives to CircleCI, Jenkins, and Travis CI?
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.
Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
Concourse
Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
CloudBees
Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud.
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.
See all alternatives
What tools integrate with CircleCI?
What tools integrate with Jenkins?
What tools integrate with Travis CI?
    No integrations found
    Decisions about CircleCI, Jenkins, and Travis CI
    Travis CI
    CircleCI

    I initially chose CircleCI for a personal project because I was not satisified with using Travis CI in the past. When it came time to develop my CI/CD config on Circle, I was pleasantly surprised with the fantastic documentation, invaluable collection of example configs and helpful support provided. The free tier they provide is quite robust for most small projects and the platform is updated frequently with nice features.

    Areas where CircleCI could improve:

    • the UI is a bit slow (you can feel the local machine straining to load all the code) and it is not as intuitive as it could be
    • many UI elements receive updates and/or changes that are not always reflected in the current docs
    See more
    Tim Abbott
    Tim Abbott
    Founder at Zulip · | 10 upvotes · 13.1K views
    atZulipZulip
    CircleCI
    Travis CI

    We actually started out on Travis CI, but we've migrated our main builds to CircleCI, and it's been a huge improvement.

    The reason it's been a huge improvement is that Travis CI has a fundamentally bad design for their images, where they start with a standard base Linux image containing tons of packages (several versions of postgres, every programming language environment, etc). This is potentially nice for the "get builds for a small project running quickly" use case, but it's a total disaster for a larger project that needs a decent number of dependencies and cares about the performance and reliability of their build.

    This issue is exacerbated by their networking infrastructure being unreliable; we usually saw over 1% of builds failing due to transient networking errors in Travis CI, even after we added retries to the most frequently failing operations like apt update or pip install. And they never install Ubuntu's point release updates to their images. So doing an apt update, apt install, or especially apt upgrade would take forever. We ended up writing code to actually uninstall many of their base packages and pin the versions of hundreds of others to get a semi-fast, semi-reliable build. It was infuriating.

    The CircleCI v2.0 system has the right design for a CI system: we can customize the base image to start with any expensive-to-install packages we need for our build, and we can update that image if and when we want to. The end result is that when migrating, we were able to delete all the hacky optimizations mentioned above, while still ending up with a 50% faster build latency. And we've also had 5-10x fewer issues with networking-related flakes, which means one doesn't have to constantly check whether a build failure is actually due to an issue with the code under test or "just another networking flake".

    See more
    Travis CI
    CircleCI
    Google Cloud Build

    I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

    I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

    One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

    Feel free to checkout an example: Cloudbuild Example

    See more
    Interest over time
    Reviews of CircleCI, Jenkins, and Travis CI
    Review ofCircleCICircleCI

    I use CircleCI as part of a cross platform mobile app to build and test the app as well as deploying .apk files to an s3 bucket.

    Alongside CircleCI this repo also has a TravisCI setup for iOS. The CircleCI build has always been quicker and since moving from CircleCI v1 to CircleCI v2 it blows the TravisCI build out of the water. I'm really impressed with the performance gains from moving to v2. I'm pretty sure I could achieve similar results in Travis as well, but it was really easy to setup the Android CI build in Circle making use of Docker.

    Avatar of tschellenbach
    CEO at Stream
    Review ofTravis CITravis CI

    In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!

    Avatar of regentgal
    VP of Engineering at Jetpack Workflow
    Review ofCircleCICircleCI

    After trying several CI systems, we stuck with CircleCI because of the inference engine in CircleCI 1.0 made setup a breeze. We were up and running quickly. Builds are reliable, nicely integrated into GitHub, and anytime we've had a question, the support team was there to help. The 2.0 system provides Docker support and far more customization and is still fairly easy to set up with helpful documentation.

    Review ofCircleCICircleCI

    CircleCI has become our CI of choice. The UI is really good and it has all the integrations we need. The 2.0 upgrade was not yet possible for one of our projects due to outdated gems, however, I have been able to get it working for a different one.

    Avatar of ryuzaki01
    Information Technology
    Review ofCircleCICircleCI

    It help us with the automated build and test and also provide us with the build artifacts which we can use for the deployment also give use archive for each of our build, this things save us alot of time and cost

    Review ofCircleCICircleCI

    We use CircleCI to deploy to server. It is much easier than other websites like Travis especially for the free tier. It is especially useful for open source projects that need private access behind the scenes.

    How developers use CircleCI, Jenkins, and Travis CI
    Avatar of datapile
    datapile uses Travis CITravis CI

    Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

    It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

    Avatar of AngeloR
    AngeloR uses CircleCICircleCI

    We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications.

    Avatar of Jeff Flynn
    Jeff Flynn uses CircleCICircleCI

    We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.

    Avatar of Kalibrr
    Kalibrr uses JenkinsJenkins

    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.

    Avatar of Matt Welke
    Matt Welke uses CircleCICircleCI

    Used for CI/CD for all proofs of concept and personal projects, because of ease of use, GitHub integrations, and free tier.

    Also used for example repos hosted in GitHub, paired with Dependabot, so that example repo dependencies are kept up to date.

    Avatar of Wirkn Inc.
    Wirkn Inc. uses JenkinsJenkins

    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.

    Avatar of Bùi Thanh
    Bùi Thanh uses JenkinsJenkins
    • 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.
    Avatar of Pēteris Caune
    Pēteris Caune uses Travis CITravis CI

    While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.

    Avatar of AngeloR
    AngeloR uses JenkinsJenkins

    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.

    Avatar of Trusted Shops GmbH
    Trusted Shops GmbH uses JenkinsJenkins

    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.

    Avatar of Dieter Adriaenssens
    Dieter Adriaenssens uses Travis CITravis CI

    Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

    Avatar of Marc3842h
    Marc3842h uses CircleCICircleCI

    CircleCI is used as continues integration system for shiro and all of its modules.

    It automatically deploys the latest GitHub commit to https://shiro.host/.

    Avatar of Nate Ferrell
    Nate Ferrell uses Travis CITravis CI

    Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

    Avatar of jasonmjohnson
    jasonmjohnson uses CircleCICircleCI

    CircleCI will be used for deployment and continuous integration using a scripted configuration that deploys to Amazon EC2.

    Avatar of Andrew Williams
    Andrew Williams uses Travis CITravis CI

    To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

    How much does CircleCI cost?
    How much does Jenkins cost?
    How much does Travis CI cost?
    Pricing unavailable