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."This solution has helped us in automating the build and test process, reducing time."
"This is a great integration tool and very powerful."
"The most valuable feature is its ability to connect with different tools and technologies."
"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."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"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."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"It could be cheaper."
"The documentation could be more friendly, and more examples of how to use it."
"It would be helpful if they had a bit more interactive UI."
"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."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"The UI of Jenkins could improve."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"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 Harness, Bamboo, 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.