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

"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"Everything in Harness is configured and runs smoothly."
"It's a highly customizable DevOps tool."
"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."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"It's very easy to learn."
"The most valuable feature of Jenkins is its open source."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"Jenkins' most valuable feature is Pipeline."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."
 

Cons

"Harness setup and configurations could be made easier to configure, which would be helpful."
"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."
"Even with automation, there's a requirement for manual change requests for approvals."
"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."
"We cannot change the ownership of any directory or file or any kind of directory."
"The enterprise version is less stable than the open-source version."
"The solution's UI can use a facelift and the logs can use more detailed information."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"I would like to see even more integrations included in the next release."
"The documentation is not helpful, as it is not user-friendly."
"The scriptwriting process could be improved in this solution in the future."
 

Pricing and Cost Advice

Information not available
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"It is an open source."
"​It is free.​"
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"It is a free product."
"The solution is open source."
"There is no cost. It is open source."
"In our company, we do pay for the licensing of the solution."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
870,701 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
30%
Computer Software Company
11%
Manufacturing Company
7%
Government
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?
Harness setup and configurations could be made easier to configure, which would be helpful.
What is your primary use case for Harness?
In Harness, we are basically using Canary type deployments. We have applications, web applications, and web servers. Whenever we get the WAR file with 50 servers in a load balancer, Harness will de...
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.
870,701 professionals have used our research since 2012.