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

Harness 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

Harness
Ranking in Build Automation
10th
Average Rating
7.8
Reviews Sentiment
7.9
Number of Reviews
4
Ranking in other categories
Static Application Security Testing (SAST) (29th), Cloud Cost Management (12th)
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
 

Mindshare comparison

As of July 2025, in the Build Automation category, the mindshare of Harness is 7.5%, up from 4.3% compared to the previous year. The mindshare of Jenkins is 10.5%, down from 12.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

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

"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"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."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"This is a great integration tool and very powerful."
"The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins."
"It is easy to use."
"Jenkins is a CI/CD tool and is the most robust tool."
"Jenkins is a very mature product."
"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."
"Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."
"Has a good interface, is reliable and saves time."
 

Cons

"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."
"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"The UI of Jenkins could improve."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"It could be cheaper."
"The learning curve is quite steep at the moment."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"The documentation is not helpful, as it is not user-friendly."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
 

Pricing and Cost Advice

Information not available
"The tool is open-source."
"It's free software with a big community behind it, which is very good."
"It is a free product."
"It is an open source."
"I used the free OSS version all the time. It was enough for all my needs."
"Jenkins is a free open-source server."
"Jenkins is open source."
"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."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
861,524 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
33%
Computer Software Company
12%
Government
7%
Retailer
5%
Financial Services Firm
22%
Computer Software Company
16%
Manufacturing Company
12%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment.
What is your primary use case for Harness?
Our primary use case for Harness ( /products/harness-reviews ) is as a deployment tool. Although I am not a DevOps engineer, my team uses Harness ( /products/harness-reviews ) for deployment purpos...
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

 

Also Known As

Armory
No data available
 

Overview

 

Sample Customers

Linedata, Openbank, Home Depot, Advanced
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Find out what your peers are saying about Harness vs. Jenkins and other solutions. Updated: July 2025.
861,524 professionals have used our research since 2012.