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

CloudBees vs Travis CI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 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

CloudBees
Ranking in Build Automation
6th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
20
Ranking in other categories
Configuration Management (11th), Value Stream Management Software (2nd), DevSecOps (3rd)
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 June 2025, in the Build Automation category, the mindshare of CloudBees is 1.4%, up from 0.2% compared to the previous year. The mindshare of Travis CI is 0.8%, down from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

YashBrahmani - PeerSpot reviewer
Offers a clear visualization and overview of workflows and helpful in managing CI/CD processes
Improvement in the sense that they can do better in terms of management of logs and stuff like that because the console logs are very extensive, and that causes a lot of storage issues. That is one of the things which is there. Also, with respect to the traditional platform and the modern platform, many things have upgraded, and it has quite improved. But when we talk about the performance of the agents, it’s still very crucial because it’s not up to par. It takes a lot of time to provision the agent and to finish the build because of the SSH connection and the JNLP connection. Due to that, sometimes the agent doesn’t get provisioned. Those are some of the blockers that meet up the time in terms of administering the instance.
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

"CloudBees operates seamlessly. Deploying to a cluster is straightforward—just one click, and the job is done."
"CloudBees's user interface is very simple and user-friendly."
"The customer support is good. You get good representatives from CloudBees to help you and understand your requirements."
"It can manage multiple Jenkins instances."
"The most valuable feature of the solution is that its GUI is quite simple."
"The initial setup is easy."
"The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar, management master to CloudBees, Blue Ocean, JobConfig, and support."
"CloudBees updates its features frequently, so if we need something like SSL login, they enable it."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"If you're logged in and working for about thirty minutes and then go idle for five to ten minutes, Jenkins will prompt you to re-authenticate."
"I think a preview of the errors would be good just at the point where the error occurs."
"A lot of stability issues are there with CloudBees."
"The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times."
"The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it."
"One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time."
"We did face some challenges, particularly with the infrastructure."
"The platform could integrate better with other tools and support external tools directly."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
857,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Manufacturing Company
13%
Legal Firm
11%
Computer Software Company
9%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with CloudBees?
There are connection issues with CloudBees, specifically between Sybase and CloudBees. We often encounter connection problems, and there are issues with the pipelines.
What is your primary use case for CloudBees?
We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.
What advice do you have for others considering CloudBees?
I would recommend CloudBees to others because building jobs is much easier than with other solutions.
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

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: June 2025.
857,028 professionals have used our research since 2012.