Try our new research platform with insights from 80,000+ expert users

Jenkins vs Travis CI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 23, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
No ranking in other categories
Travis CI
Ranking in Build Automation
21st
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the Build Automation category, the mindshare of Jenkins is 10.6%, down from 14.0% compared to the previous year. The mindshare of Travis CI is 0.6%, down from 2.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.
Pravar Agrawal - PeerSpot reviewer
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Jenkins is particularly valuable since it saves time by automating manual tasks."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"It's a powerful tool for CI/CD."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"Distributed execution of build and test jobs."
"Has a good interface, is reliable and saves time."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"Jenkins has a lot of built-in packages and tools."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"There are some issues with Jenkins, especially with the SIP job."
"The major drawback with Jenkins is the lack of support."
"They need to improve their documentation."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"Jenkins takes a long time to create archive files."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"Jenkins is not expensive and reasonably priced."
"Jenkins is open source."
"The solution is one of the lowest costs compared to competitors."
"Jenkins is a free solution, it is open source."
"I used the free OSS version all the time. It was enough for all my needs."
"​It is free.​"
"The solution is open source."
"It is a free product."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
842,194 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

Comparisons

 

Overview

 

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: March 2025.
842,194 professionals have used our research since 2012.