AWS CodePipeline vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
4,635 views|3,586 comparisons
92% willing to recommend
Jenkins Logo
6,536 views|5,610 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between AWS CodePipeline and Jenkins based on real PeerSpot user reviews.

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed AWS CodePipeline vs. Jenkins Report (Updated: May 2024).
772,649 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
"The integrations are good.""I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly.""Code deployment is the best feature.""The product is cost-effective and integrates well with the AWS environment.""The product is a one-stop solution that you can use to integrate, deploy and host your application.""AWS CodePipeline has valuable integration features.""The integration with other applications is fabulous.""The most valuable feature of AWS CodePipeline is the flexibility of the configuration."

More AWS CodePipeline Pros →

"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 solution is scalable and concurrent users have access to the platform.""Jenkins has been instrumental in automating our build and deployment processes.""The initial setup is pretty simple.""We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit.""I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company.""It's very useful when you want to automate different processes from beginning to end.""For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."

More Jenkins Pros →

Cons
"It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks.""The tool does not provide automated features for evidence collection.""The support team’s response time must be improved.""The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation.""In the next release, I would like to see fewer timeout errors.""The setup time is a bit long.""There could be a possibility of deploying tag-based conditions for different environments using the same code base.""The migration process from one source code to another needs improvement."

More AWS CodePipeline Cons →

"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 relies on the old version of interface for configuration management. This needs improvement.""The documentation could be more friendly, and more examples of how to use it.""Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help.""The solution could improve by having more advanced integrations.""The learning curve is quite steep at the moment.""Logging could be improved to offer a clearer view.""Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."

More Jenkins Cons →

Pricing and Cost Advice
  • "The pricing of this solution is dependent upon your needs including how many jobs you daily and how many times the developer will be changing codes and completing deployments."
  • "I would rate the product's pricing a five out of ten."
  • "AWS offers free business or enterprise support services."
  • "It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
  • "The product is quite expensive compared to other solutions."
  • "AWS CodePipeline is quite affordable. I've been running around four pipelines and the cost is around one dollar per month. It rarely exceeds two dollars."
  • "Compared to other cloud services, AWS CodePipeline falls a bit more on the pricey side. I see that the price of the product has been increasing for the past few years."
  • More AWS CodePipeline 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 Build Automation solutions are best for your needs.
    772,649 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:Both AWS solutions deliver solid options, with uniquely different features. AWS CodeStar allows for quick development, building, and deployments of apps. It also provides web application and web… more »
    Top Answer:The product is quite expensive compared to other solutions.
    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
    3rd
    out of 42 in Build Automation
    Views
    4,635
    Comparisons
    3,586
    Reviews
    12
    Average Words per Review
    395
    Rating
    8.2
    2nd
    out of 42 in Build Automation
    Views
    6,536
    Comparisons
    5,610
    Reviews
    37
    Average Words per Review
    382
    Rating
    7.9
    Comparisons
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Harness logo
    Compared 7% of the time.
    Tekton logo
    Compared 7% of the time.
    Also Known As
    CodePipeline
    Learn More
    Overview

    AWS CodePipeline is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define. This enables you to rapidly and reliably deliver features and updates. You can easily integrate AWS CodePipeline with third-party services such as GitHub or with your own custom plugin. With AWS CodePipeline, you only pay for what you use. There are no upfront fees or long-term commitments.

    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
    Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    REVIEWERS
    Computer Software Company20%
    Transportation Company10%
    Comms Service Provider10%
    Government10%
    VISITORS READING REVIEWS
    Computer Software Company20%
    Financial Services Firm14%
    Comms Service Provider7%
    Manufacturing Company7%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    REVIEWERS
    Small Business40%
    Midsize Enterprise20%
    Large Enterprise40%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise13%
    Large Enterprise62%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    AWS CodePipeline vs. Jenkins
    May 2024
    Find out what your peers are saying about AWS CodePipeline vs. Jenkins and other solutions. Updated: May 2024.
    772,649 professionals have used our research since 2012.

    AWS CodePipeline is ranked 3rd in Build Automation with 13 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. AWS CodePipeline is rated 8.4, while Jenkins is rated 8.0. The top reviewer of AWS CodePipeline writes "A fully managed service with excellent integrations and a flexible architecture". 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". AWS CodePipeline is most compared with GitLab, AWS CodeStar, GitHub Actions, Tekton and Bamboo, whereas Jenkins is most compared with GitLab, Bamboo, IBM Rational Build Forge, Harness and Tekton. See our AWS CodePipeline vs. Jenkins report.

    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.