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

CloudBees vs Harness comparison

 

Comparison Buyer's Guide

Executive Summary

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
7th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
20
Ranking in other categories
Configuration Management (12th), Value Stream Management Software (3rd), DevSecOps (5th)
Harness
Ranking in Build Automation
11th
Average Rating
7.6
Reviews Sentiment
7.7
Number of Reviews
3
Ranking in other categories
Static Application Security Testing (SAST) (30th), Cloud Cost Management (15th)
 

Mindshare comparison

As of February 2025, in the Build Automation category, the mindshare of CloudBees is 0.9%, up from 0.2% compared to the previous year. The mindshare of Harness is 5.8%, up from 4.3% 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.
Linwei Yuan - PeerSpot reviewer
Streamline microservices deployment with integrated execution pipelines and comprehensive monitoring
Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place. It is very convenient since we have many microservices, so having one platform for all of them is beneficial. The dashboard allows me to monitor all core services' deployment status in one place, making it easier to find bugs and check logs.

Quotes from Members

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

Pros

"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 most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."
"The most valuable feature of the solution is that its GUI is quite simple."
"The solution's most valuable feature is its flexibility."
"It’s a very good tool for auditing your project pipelines as well."
"The security audit product offered by CloudBees is particularly beneficial in automating audit processes, which reduces the time developers spend on audits."
"CloudBees's user interface is very simple and user-friendly."
"It can manage multiple Jenkins instances."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."
"It's a highly customizable DevOps tool."
 

Cons

"To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture."
"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."
"I think a preview of the errors would be good just at the point where the error occurs."
"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"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."
"We've noticed occasional issues with folder permissions changing unexpectedly. Specifically, permissions sometimes shift from the CloudBees user to the root user. This can cause pipeline failures, as pipelines require the correct CloudBees user permissions to execute properly."
"Sometimes, there are performance issues, however, they may be due to our organization's configuration."
"A lot of stability issues are there with CloudBees."
"Even with automation, there's a requirement for manual change requests for approvals."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Manufacturing Company
14%
Legal Firm
12%
Non Profit
7%
Financial Services Firm
34%
Computer Software Company
13%
Government
6%
Manufacturing Company
6%
 

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 do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
Previously, when deploying a version that had been deployed successfully before, it sometimes failed upon trying again, which seems to be an intermittent issue about stability. I prefer the previou...
What is your primary use case for Harness?
I used Harness for CICD, and it served as the release platform that our team used for Java applications. We do Java microservices, and we used it to deploy them.
 

Comparisons

 

Also Known As

No data available
Armory
 

Overview

 

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Linedata, Openbank, Home Depot, Advanced
Find out what your peers are saying about CloudBees vs. Harness and other solutions. Updated: January 2025.
832,138 professionals have used our research since 2012.