AWS CodePipeline vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
4,776 views|3,717 comparisons
92% willing to recommend
Jenkins Logo
6,756 views|5,825 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).
771,740 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 tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier.""The integration with other applications is fabulous.""It's a perfect solution if you are just using AWS.""The product is cost-effective and integrates well with the AWS environment.""The integrations are good.""I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly.""It helps develop CI/CD implementations with centralized management of code building, deployment, and version control.""In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."

More AWS CodePipeline Pros →

"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available.""A lot of support material exists via a single web search of exactly what you're looking for.""It is a stable solution.""Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins.""Jenkins has a lot of built-in packages and tools.""Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case.""Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead.""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."

More Jenkins Pros →

Cons
"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 product’s pricing needs improvement.""The migration process from one source code to another needs improvement.""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 tool does not provide automated features for evidence collection."

More AWS CodePipeline Cons →

"The learning curve is quite steep at the moment.""Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere.""Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly.""The user interface could be updated a little.""Jenkins relies on the old version of interface for configuration management. This needs improvement.""Some kind of SaaS product would be helpful in providing organizational structure.""Jenkins takes a long time to create archive files.""The scriptwriting process could be improved in this solution in the future."

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.
    771,740 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 41 in Build Automation
    Views
    4,776
    Comparisons
    3,717
    Reviews
    12
    Average Words per Review
    395
    Rating
    8.2
    2nd
    out of 41 in Build Automation
    Views
    6,756
    Comparisons
    5,825
    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.
    Tekton logo
    Compared 6% 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
    REVIEWERS
    Computer Software Company20%
    Transportation Company10%
    Comms Service Provider10%
    Government10%
    VISITORS READING REVIEWS
    Computer Software Company19%
    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.
    771,740 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, 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.