We performed a comparison between Jenkins and JFrog Pipeline 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."Having builds and test tasks triggered on commit helps not to break the product."
"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."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"It is a stable solution."
"The deployment of traditional Jenkins is easy."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Jenkins' most valuable feature is Pipeline."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."
"Testing against multiple run times, versions, and environments is a plus point with the additional pipelines making it more interesting to see what is happening across your development process in a single pane of glass."
"Logging could be improved to offer a clearer view."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"The solution's UI can use a facelift and the logs can use more detailed information."
"Jenkins takes a long time to create archive files."
"Jenkins needs a faster deployment process."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"They could work on reducing the number of permissions required while using Bitbucket."
Earn 20 points
Jenkins is ranked 2nd in Build Automation with 83 reviews while JFrog Pipeline is ranked 22nd in Build Automation. Jenkins is rated 8.0, while JFrog Pipeline is rated 8.0. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of JFrog Pipeline writes "Testing against multiple run times, versions, and environments is a plus point". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and GNU Make, whereas JFrog Pipeline is most compared with Bamboo, Harness, TeamCity and GitHub Actions.
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.
