Jenkins vs Travis CI comparison

Jenkins and Travis CI are both solutions in the Build Automation category. Jenkins is ranked #3 with an average rating of 8.1, while Travis CI is ranked #21 with an average rating of 6.0. Jenkins holds a 11.0% mindshare in BA, compared to Travis CI’s 0.7% mindshare. Additionally, 87% of Jenkins users are willing to recommend the solution.

Jenkins

Read 93 Jenkins reviews

4,563 Views
3,948 Comparison Views

87% willing to recommend

Travis CI

Read 2 Travis CI reviews

423 Views
460 Comparison Views

0% willing to recommend

Jenkins

Travis CI

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Jan 23, 2025

Jenkins and Travis CI are competing CI/CD tools tailored for different development environments. Jenkins offers more flexibility due to its extensive plugin library, while Travis CI’s ease of integration and straightforward setup give it an advantage for smaller projects or teams.

Features: Jenkins is known for its wide array of plugins, strong community support, and high customizability, making it suitable for varied project needs. Travis CI provides native cloud service integration, automatic testing features, and simplicity, ensuring a smooth user experience.

Ease of Deployment and Customer Service: Jenkins grants greater control over deployment through its on-premise installations, though it may require more setup and maintenance. Travis CI, being cloud-based, reduces infrastructure demands and allows faster deployments. Its customer service aligns with its cloud-first model, facilitating rapid deployment strategies.

Pricing and ROI: Jenkins is open-source, minimizing initial setup costs but possibly incurring higher long-term costs due to hosting and maintenance. Travis CI has a clear pricing model based on usage, potentially cost-effective for smaller teams or projects. Jenkins delivers better ROI for large enterprises through customization and scalability, while Travis CI offers economical solutions for smaller teams needing quick deployment without significant infrastructure investments.

To learn more, read our detailed Build Automation Report (Updated: January 2025).

Buyer's Guide

Build Automation

January 2025

Download the complete report

Helped 838,640 peers since 2012

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

6.9

Number of Reviews

Ranking in other categories

No ranking in other categories

Travis CI

Ranking in Build Automation

21st

Average Rating

6.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

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

Build Automation

Featured Reviews

Dinesh-Patil

Consultant at a manufacturing company with 10,001+ employees

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.

Read full review

Pravar Agrawal

Senior SRE at IBM

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.

Read full review

Quotes from Members

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

Pros

"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."

"It's very useful when you want to automate different processes from beginning to end."

"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."

"It is easy to use."

"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."

"Has enabled full automation of the company."

"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."

"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."

More Jenkins pros

"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."

Cons

"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."

"The bug fix speed is very slow."

"Partition security for the workflow of projects is not yet an option."

"Jenkins could improve the integration with other platforms."

"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."

"The major drawback with Jenkins is the lack of support."

"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."

"Jenkins needs a faster deployment process."

More Jenkins cons

"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."

Pricing and Cost Advice

"Jenkins is a free solution, it is open source."

"Jenkins is open source and free."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"Jenkins is open source."

"Jenkins is a free open-source server."

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."

"In our company, we do pay for the licensing of the solution."

"It is a cheap solution."

More Jenkins pricing and cost advice

Information not available

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

838,640 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

22%

Computer Software Company

17%

Manufacturing Company

11%

Government

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

See all answers

What do you like most about Jenkins?

Jenkins has been instrumental in automating our build and deployment processes.

See all answers

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.

See all answers

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.

See all answers

What needs improvement with Travis CI?

See all answers

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

See all answers

Comparisons

GitLab vs Jenkins

Compared 16% of the time

Harness vs Jenkins

Compared 13% of the time

Bamboo vs Jenkins

Compared 11% of the time

Bazel vs Jenkins

Compared 9% of the time

AWS CodePipeline vs Jenkins

Compared 7% of the time

More Jenkins Competitors

Tekton vs Travis CI

Compared 100% of the time

More Travis CI Competitors

Product Reports

Buyer's Guide

Jenkins

February 2025

Download Jenkins product report

Buyer's Guide

Build Automation

January 2025

Download Travis CI product report

Overview

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

Jenkins

Easily sync your GitHub projects with Travis CI and you'll be testing your code in minutes. Travis CI for private repositories has plans for every size project. With Travis CI testing your open source project is 100% free.

Travis CI

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: January 2025.

DOWNLOAD NOW

838,640 professionals have used our research since 2012.

See our list of best Build Automation vendors.

We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.