Jenkins聽vs聽Travis CI

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

Jenkins

38.8K
31.4K
+ 1
2.2K
Travis CI

7.4K
5.2K
+ 1
1.8K
Add tool

Jenkins vs Travis CI: What are the differences?

What is Jenkins? An extendable open source continuous integration server. 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? A hosted continuous integration service for open source and private projects. 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.

Jenkins and Travis CI can be categorized as "Continuous Integration" tools.

Some of the features offered by Jenkins are:

  • Easy installation
  • Easy configuration
  • Change set support

On the other hand, Travis CI provides the following key features:

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

"Hosted internally", "Free open source" and "Great to build, deploy or launch anything async" are the key factors why developers consider Jenkins; whereas "Github integration", "Free for open source" and "Easy to get started" are the primary reasons why Travis CI is favored.

Jenkins is an open source tool with 13.3K GitHub stars and 5.48K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.

Facebook, Netflix, and Instacart are some of the popular companies that use Jenkins, whereas Travis CI is used by Lyft, Heroku, and Rainist. Jenkins has a broader approval, being mentioned in 1774 company stacks & 1526 developers stacks; compared to Travis CI, which is listed in 670 company stacks and 624 developer stacks.

Advice on Jenkins and Travis CI
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 路 148.7K 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 路 137K 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 路 57.4K 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 Travis CI
Pedro Gil Carvalho
Head of Engineering at Lengoo GmbH | 3 upvotes 路 1.5K 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

When choosing a tool to help automate our CI/CD, the decision came down to GitHub Actions (GA) or TravisCI. Both are great, but the team has more experience with GA. Given GAs broad support of languages and workflows, it's hard to go wrong with this decision. We will also be using GitHub for version control and project management, so having everything in one place is convenient.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Jenkins
Pros of Travis CI
  • 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
  • 508
    Github integration
  • 388
    Free for open source
  • 272
    Easy to get started
  • 191
    Nice interface
  • 163
    Automatic deployment
  • 72
    Tutorials for each programming language
  • 40
    Friendly folks
  • 29
    Support for multiple ruby versions
  • 28
    Osx support
  • 24
    Easy handling of secret keys
  • 6
    Fast builds
  • 4
    Support for students
  • 3
    The best tool for Open Source CI
  • 3
    Hosted
  • 3
    Build Matrices
  • 2
    Straightforward Github/Coveralls integration
  • 2
    Easy of Usage
  • 2
    Github Pull Request build
  • 2
    Integrates with everything
  • 1
    Docker support
  • 1
    Configuration saved with project repository
  • 1
    Free for students
  • 1
    Build matrix
  • 1
    No-brainer for CI
  • 1
    Debug build workflow
  • 1
    Great Documentation
  • 1
    Multi-threaded run
  • 1
    Hipchat Integration
  • 1
    Caching resolved artifacts
  • 1
    Ubuntu trusty is not supported
  • 0
    Perfect
  • 0
    One

Sign up to add or upvote prosMake informed product decisions

Cons of Jenkins
Cons of Travis CI
  • 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
  • 8
    Can't be hosted insternally
  • 3
    Feature lacking
  • 3
    Unstable
  • 2
    Incomplete documentation for all platforms

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

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

What companies use Jenkins?
What companies use Travis CI?
See which teams inside your own company are using Jenkins or Travis CI.
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 Travis CI?

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
1116
+4
4
1660
Dec 4 2019 at 8:01PM

Pinterest

+4
5
2883
+42
46
38825
What are some alternatives to Jenkins and Travis CI?
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.
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.
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
Reviews of Jenkins and Travis CI
Review of
Travis 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!

How developers use Jenkins and Travis CI
datapile uses
Travis 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).

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.

Dieter Adriaenssens uses
Travis 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.

Nate Ferrell uses
Travis 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.

Andrew Williams uses
Travis CI

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

Sascha Manns uses
Travis CI

Travis provides more than one Ruby version setting. So i can test my push directly in different Ruby versions.