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
7th
Average Rating
8.0
Reviews Sentiment
7.8
Number of Reviews
5
Ranking in other categories
Static Application Security Testing (SAST) (18th), Cloud Cost Management (8th)
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 October 2025, in the Build Automation category, the mindshare of Harness is 6.9%, up from 4.8% compared to the previous year. The mindshare of Jenkins is 9.1%, down from 11.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Jenkins9.1%
Harness6.9%
Other84.0%
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

"Everything in Harness is configured and runs smoothly."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"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, making it convenient."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"It's a highly customizable DevOps tool."
"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."
"The most valuable feature of Jenkins is its open source."
"Jenkins has excellent task planning features."
"It is easy to use."
"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."
"This solution has helped us in automating the build and test process, reducing time."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"Jenkins' most valuable feature is Pipeline."
 

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."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"Harness setup and configurations could be made easier to configure, which would be helpful."
"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."
"It would be helpful if they had a bit more interactive UI."
"It could be cheaper."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective."
"I do not have any notes for improvement."
"The UI of Jenkins could improve."
 

Pricing and Cost Advice

Information not available
"In our company, we do pay for the licensing of the solution."
"The solution is open source."
"It's free software with a big community behind it, which is very good."
"​It is free.​"
"Jenkins is not expensive and reasonably priced."
"It is an open source."
"Jenkins is an open-source tool."
"Jenkins is open source and free."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
868,787 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
31%
Computer Software Company
11%
Government
6%
Manufacturing Company
6%
Financial Services Firm
20%
Manufacturing Company
13%
Computer Software Company
13%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise15
Large Enterprise56
 

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: September 2025.
868,787 professionals have used our research since 2012.