Heroku vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Heroku Logo
4,273 views|3,175 comparisons
85% 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 Heroku and Jenkins based on real PeerSpot user reviews.

Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Oracle and others in PaaS Clouds.
To learn more, read our detailed PaaS Clouds Report (Updated: March 2024).
768,857 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
"I like the tool's scalability, CLI, and dashboards.""The platform is very Node.js-friendly, which is something that is important to us.""It is easy to deploy applications, and we don't need to bother about software updates on the server. We don't need to bother about machines, servers, and hardware. We only need to care about the system and functionality that we need or want to develop. They take care of everything else. It provides high availability. It is a pretty good solution that provides everything that we need. It has everything that we need to run our applications. We have many different applications, and we generate three million bills for a company in Brazil. We see more than a billion requests per day in another application. Everything works just fine, and it is very good.""What I found most valuable about this solution is that it's easy to use and integrate with GitHub actions.""One of the best things about Heroku is that it is very easy and straightforward to deploy an application.""It's easy to push a change and to deploy new things.""Thanks to Heroku, we don't need to do as much direct management in AWS.""The most valuable feature of Heroku is the continuous integration and applications it provides."

More Heroku Pros →

"It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins.""It's very useful when you want to automate different processes from beginning to end.""The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud.""We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically.""The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle.""Jenkins is very user-friendly.""It's very easy to learn.""It can scale easily."

More Jenkins Pros →

Cons
"They could flesh out some of their analytics a little more.""The tool's configuration is complex.""We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert.""We don't find the pipelines intuitive. The user experience could be better. Having to set up multiple apps, then a pipeline, seems like an overkill on the amount of work to do.""Their support is good, but they can improve their response time.""Heroku had an authentication problem a few months ago, but they solved it.""I improved the application performance by monitoring and adjusting the cleaner configuration to help set better lightweight limits on containers that run the app instances.""We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."

More Heroku Cons →

"There is no way for the cloud repositories to trigger Jenkins.""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.""This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful.""Jenkins could improve the integration with other platforms.""Support should be provided at no cost, as there is no free support available for any of the free versions.""The enterprise version is less stable than the open-source version.""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.""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."

More Jenkins Cons →

Pricing and Cost Advice
  • "Its price is very good."
  • "The price of Heroku could be less expensive."
  • "There is a standard fee for a processing unit, they call them "dynos," and then you pay for add-ons."
  • "I rate the tool's pricing a three out of ten."
  • "The tool is free."
  • More Heroku 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 →

    report
    Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
    768,857 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:I like the tool's scalability, CLI, and dashboards.
    Top Answer:I improved the application performance by monitoring and adjusting the cleaner configuration to help set better lightweight limits on containers that run the app instances.
    Top Answer:We use the solution to streamline mobile application deployment and management. By connecting our project's GitHub repository to Heroku, I enabled automatic deployments whenever changes were pushed to… 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
    13th
    out of 37 in PaaS Clouds
    Views
    4,273
    Comparisons
    3,175
    Reviews
    4
    Average Words per Review
    307
    Rating
    8.0
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    Microsoft Azure logo
    Compared 35% of the time.
    Google Cloud logo
    Compared 13% of the time.
    Google App Engine logo
    Compared 8% of the time.
    OpenShift logo
    Compared 7% of the time.
    Pivotal Cloud Foundry logo
    Compared 6% 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.
    Tekton logo
    Compared 7% of the time.
    Learn More
    Overview

    Established in 2007, Heroku is a cloud application platform providing a streamlined, efficient place for web app developers to create and deploy their applications. Heroku is designed to maximize developer productivity. With the entire web application development process available on the Herokucloud, creating and rolling out web apps has been made more efficient, convenient, and cost-effective than ever before.

    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
    Facebook, UrbanDictionary, Code for America, Mailchimp, Rapportive, GitHub, TED, and Lyft.
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    REVIEWERS
    Computer Software Company43%
    Marketing Services Firm14%
    Sports Company14%
    Agriculture14%
    VISITORS READING REVIEWS
    Computer Software Company14%
    Educational Organization13%
    Comms Service Provider11%
    Financial Services Firm8%
    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
    REVIEWERS
    Small Business81%
    Midsize Enterprise8%
    Large Enterprise12%
    VISITORS READING REVIEWS
    Small Business21%
    Midsize Enterprise14%
    Large Enterprise65%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    PaaS Clouds
    March 2024
    Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Oracle and others in PaaS Clouds. Updated: March 2024.
    768,857 professionals have used our research since 2012.

    Heroku is ranked 13th in PaaS Clouds with 27 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. Heroku is rated 8.4, while Jenkins is rated 8.0. The top reviewer of Heroku writes "Useful for mobile and web applications, and helps with rapid development cycle ". 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". Heroku is most compared with Microsoft Azure, Google Cloud, Google App Engine, OpenShift and Pivotal Cloud Foundry, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Tekton.

    We monitor all PaaS Clouds 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.