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

Harness vs Jenkins 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

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)
Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
93
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Build Automation category, the mindshare of Harness is 5.7%, up from 4.3% compared to the previous year. The mindshare of Jenkins is 11.3%, down from 14.3% 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.
Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

Quotes from Members

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

Pros

"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, making it convenient."
"It's a highly customizable DevOps tool."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"Jenkins is very stable."
"The initial setup is simple."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."
"Jenkins is free and open source."
"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"It offers continuous deployment and continuous testing. It enables us to figure out anything."
 

Cons

"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."
"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."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"The learning curve is quite steep at the moment."
"The scriptwriting process could be improved in this solution in the future."
"The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective."
"The documentation is not helpful, as it is not user-friendly."
"Some kind of SaaS product would be helpful in providing organizational structure."
"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
 

Pricing and Cost Advice

Information not available
"It is a free product."
"Jenkins is not expensive and reasonably priced."
"It is an open source."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"​It is free.​"
"In our company, we do pay for the licensing of the solution."
"Jenkins is an open-source tool."
"The solution is open source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
831,158 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
34%
Computer Software Company
13%
Government
6%
Manufacturing Company
6%
Financial Services Firm
23%
Computer Software Company
16%
Manufacturing Company
11%
Government
6%
 

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

Learn More

Video not 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: January 2025.
831,158 professionals have used our research since 2012.