JFrog Pipeline vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Jenkins Logo
6,756 views|5,825 comparisons
88% willing to recommend
JFrog Logo
318 views|289 comparisons
100% willing to recommend
Comparison Buyer's Guide
Executive Summary

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.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
771,157 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
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins.""Jenkins has built good plugins and has a good security platform.""It's very useful when you want to automate different processes from beginning to end.""Jenkins is very stable.""It is very useful for us to be able to collect and manage automatic processing pipelines.""Very easy to understand for newcomers.""The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization.""The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."

More Jenkins Pros →

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

More JFrog Pipeline Pros →

Cons
"Centralized user management would be helpful.""The user interface could be updated a little.""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.""We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms.""Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on.""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.""The documentation on plugin development could be better: more examples. ​""Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."

More Jenkins Cons →

"They could work on reducing the number of permissions required while using Bitbucket."

More JFrog Pipeline Cons →

Pricing and Cost Advice
  • "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 →

  • "The pricing is the cheapest compared to the other platforms out there."
  • More JFrog Pipeline Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,157 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: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.
    Ask a question

    Earn 20 points

    Ranking
    2nd
    out of 41 in Build Automation
    Views
    6,756
    Comparisons
    5,825
    Reviews
    37
    Average Words per Review
    382
    Rating
    7.9
    22nd
    out of 41 in Build Automation
    Views
    318
    Comparisons
    289
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    Comparisons
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 10% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    GNU Make logo
    Compared 3% of the time.
    Also Known As
    Shippable
    Learn More
    Overview

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

    JFrog Pipelines empowers software teams to ship updates faster by automating DevOps processes in a continuously streamlined and secure way across all their teams and tools. Encompassing continuous integration (CI), continuous delivery (CD), infrastructure and more, it automates everything from code to production. Pipelines is natively integrated with the JFrog Platform and is available with both cloud (software-as-a-service) and on-prem subscriptions.
    Sample Customers
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    SAP, Today Tix, Cisco, Lithium, Pushspring, Packet
    Top Industries
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    No Data Available
    Company Size
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    No Data Available
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation. Updated: April 2024.
    771,157 professionals have used our research since 2012.

    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.