Harness vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Harness Logo
2,365 views|1,885 comparisons
100% willing to recommend
Jenkins Logo
6,896 views|5,921 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Harness and Jenkins based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
768,886 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"It's a highly customizable DevOps tool."

More Harness Pros →

"The initial setup is simple.""We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc.""Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases.""Very easy to understand for newcomers.""There are a large number of plugins available for integration with third party systems.""The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment.""It is very useful for us to be able to collect and manage automatic processing pipelines.""We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."

More Jenkins Pros →

Cons
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

More Harness Cons →

"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers.""It does not have a very user-friendly interface.""I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement.""The support for the latest Java Runtime Environment should be improved.""Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file.""This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful.""The documentation could be more friendly, and more examples of how to use it.""The enterprise version is less stable than the open-source version."

More Jenkins Cons →

Pricing and Cost Advice
Information Not Available
  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,886 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    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 nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer: It's a highly customizable DevOps tool.
    Top Answer:The platform's initial setup process could be simplified. Additionally, security features and capabilities for understanding vulnerabilities within the application could be enhanced directly from the… more »
    Top Answer:We use Harness for deploying Kubernetes clusters. It is a SaaS-based tool with a good graphical user interface. We can create workflows and deployment pipelines and easily visualize them. We can see… more »
    Top Answer: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 easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    12th
    out of 41 in Build Automation
    Views
    2,365
    Comparisons
    1,885
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    Tekton logo
    Compared 23% of the time.
    Bamboo logo
    Compared 15% of the time.
    TeamCity logo
    Compared 10% of the time.
    GitHub Actions logo
    Compared 9% of the time.
    GitLab logo
    Compared 7% of the time.
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Bazel logo
    Compared 5% of the time.
    Learn More
    Harness
    Video Not Available
    Overview

    Harness is the first Continuous Delivery-as-a-Service platform that uses Machine Learning to simplify the entire process of delivering code from artifact into production – quickly, safely, securely, and repeatably.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Sample Customers
    Linedata, Openbank, Home Depot, Advanced
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    VISITORS READING REVIEWS
    Financial Services Firm37%
    Computer Software Company12%
    Manufacturing Company7%
    Healthcare Company5%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    VISITORS READING REVIEWS
    Small Business14%
    Midsize Enterprise8%
    Large Enterprise78%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,886 professionals have used our research since 2012.

    Harness is ranked 12th in Build Automation with 1 review while Jenkins is ranked 2nd in Build Automation with 83 reviews. Harness is rated 7.0, while Jenkins is rated 8.0. The top reviewer of Harness writes "Provides a good graphical interface, but the initial setup process needs improvement ". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". Harness is most compared with Tekton, Bamboo, TeamCity, GitHub Actions and GitLab, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Bazel.

    See our list of best Build Automation vendors.

    We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.