We performed a comparison between Harness and Jenkins based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation."It's a highly customizable DevOps tool."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"The most valuable feature of Jenkins is its open source."
"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."
"This solution has helped us in automating the build and test process, reducing time."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"Jenkins has a lot of built-in packages and tools."
"Very easy to understand for newcomers."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"It would be helpful if they had a bit more interactive UI."
"The user interface could be updated a little."
"The documentation could be more friendly, and more examples of how to use it."
"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."
"Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI."
"A more user-friendly UI for creating pipelines would be helpful."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
Harness is ranked 8th 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.