AWS CodePipeline vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
5,021 views|3,949 comparisons
Jenkins Logo
7,158 views|6,126 comparisons
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: March 2024).
765,386 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 find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly.""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.""In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps.""It's a perfect solution if you are just using AWS.""It helps develop CI/CD implementations with centralized management of code building, deployment, and version control.""AWS CodePipeline has valuable integration features.""The most valuable feature of AWS CodePipeline is the flexibility of the configuration."

More AWS CodePipeline Pros →

"The most valuable feature of the solution is its integration between different tools.""We used it for all continuous integration parts, like automation testing, deployment, etc.""I like that you can find a wide range of plugins for Jenkins.""The most valuable feature of Jenkins is its open source.""It is a stable solution.""It can scale easily.""This solution has helped us in automating the build and test process, reducing time.""Jenkins has excellent task planning features."

More Jenkins Pros →

Cons
"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.""If there are many dependancies involved in the setup, it may take a long time.""The tool does not provide automated features for evidence collection.""If you're talking about multi-cloud, you can't use it.""AWS CodePipeline doesn't offer much room for customization."

More AWS CodePipeline Cons →

"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.""It does not have a very user-friendly interface.""The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers.""The user interface could be updated a little.""The enterprise version is less stable than the open-source version.""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.""Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."

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."
  • 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.
    765,386 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:AWS does not require upfront licenses or complex payment structures. It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model… 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
    4th
    out of 41 in Build Automation
    Views
    5,021
    Comparisons
    3,949
    Reviews
    7
    Average Words per Review
    362
    Rating
    8.1
    2nd
    out of 41 in Build Automation
    Views
    7,158
    Comparisons
    6,126
    Reviews
    37
    Average Words per Review
    388
    Rating
    7.8
    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.
    Tekton logo
    Compared 7% of the time.
    Harness logo
    Compared 6% 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
    VISITORS READING REVIEWS
    Computer Software Company19%
    Financial Services Firm14%
    Comms Service Provider8%
    Manufacturing Company7%
    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 Business40%
    Midsize Enterprise20%
    Large Enterprise40%
    VISITORS READING REVIEWS
    Small Business23%
    Midsize Enterprise13%
    Large Enterprise64%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    AWS CodePipeline vs. Jenkins
    March 2024
    Find out what your peers are saying about AWS CodePipeline vs. Jenkins and other solutions. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    AWS CodePipeline is ranked 4th in Build Automation with 10 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, Tekton, GitHub Actions and Bamboo, whereas Jenkins is most compared with GitLab, Bamboo, IBM Rational Build Forge, Tekton and Harness. 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.