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

CloudBees vs Jenkins 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 (5th)
Jenkins
Ranking in Build Automation
4th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2025, in the Build Automation category, the mindshare of CloudBees is 1.5%, up from 0.2% compared to the previous year. The mindshare of Jenkins is 10.3%, down from 12.2% 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.
Annamalai Pts - PeerSpot reviewer
Streamlined CI/CD pipelines with powerful integration and an easy setup
I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS Jenkins has made the developers' work very easy. They commit to the remote repository, and…

Quotes from Members

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

Pros

"It can manage multiple Jenkins instances."
"CloudBees is the Jenkins tool for building and deploying. There's open-source Jenkins, which is free and can be used by any organization, but it offers a different architecture for Jenkins. If your organization is larger, you might choose the architecture. This way, you can have different masters for different applications, and different teams can manage their masters separately. However, a single person can still control all the masters, whoever manages it for the organization."
"The initial setup is easy."
"The security audit product offered by CloudBees is particularly beneficial in automating audit processes, which reduces the time developers spend on audits."
"The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar, management master to CloudBees, Blue Ocean, JobConfig, and support."
"The most valuable feature of the solution is that its GUI is quite simple."
"CloudBees updates its features frequently, so if we need something like SSL login, they enable it."
"The solution's most valuable feature is its flexibility."
"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."
"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
"It's a powerful tool for CI/CD."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"Jenkins has a lot of built-in packages and tools."
"The initial setup is pretty simple."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
 

Cons

"To improve efficiency, they should focus on smoother label deployment."
"Sometimes, there are performance issues, however, they may be due to our organization's configuration."
"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 noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"I think a preview of the errors would be good just at the point where the error occurs."
"The user interface of CloudBees is good but could be even more intuitive. Improving the user-friendliness of the interface and having simpler setup configurations would greatly benefit new users."
"There are connection issues with CloudBees, specifically between Sybase and CloudBees. W"
"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."
"The support for the latest Java Runtime Environment should be improved."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"Some kind of SaaS product would be helpful in providing organizational structure."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"I would like to see even more integrations included in the next release."
"The solution's UI can use a facelift and the logs can use more detailed information."
"There are some issues with Jenkins, especially with the SIP job."
"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."
 

Pricing and Cost Advice

Information not available
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"Jenkins is open source."
"Jenkins is an open-source platform."
"It's free software with a big community behind it, which is very good."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"There is no cost. It is open source."
"​It is free.​"
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
865,576 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
23%
Manufacturing Company
12%
Legal Firm
10%
Computer Software Company
8%
Financial Services Firm
21%
Computer Software Company
14%
Manufacturing Company
13%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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

Comparisons

 

Overview

 

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Find out what your peers are saying about CloudBees vs. Jenkins and other solutions. Updated: July 2025.
865,576 professionals have used our research since 2012.