AWS CodePipeline vs Jenkins comparison

Read 93 Jenkins reviews

5,015 Views
4,320 Comparison Views

87% willing to recommend

AWS CodePipeline

Comparison Buyer's Guide

Download the report

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: December 2024).

AWS CodePipeline vs. Jenkins

Download the complete report

Helped 824,053 peers since 2012

Categories and Ranking

AWS CodePipeline

Ranking in Build Automation

4th

Average Rating

8.4

Reviews Sentiment

7.4

Number of Reviews

Ranking in other categories

No ranking in other categories

Jenkins

Ranking in Build Automation

3rd

Average Rating

8.0

Reviews Sentiment

6.9

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of December 2024, in the Build Automation category, the mindshare of AWS CodePipeline is 6.8%, down from 9.5% compared to the previous year. The mindshare of Jenkins is 11.5%, down from 14.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Udhay Prakash Pethakamsetty

Data Engineer Manager at Capgemini

A fully managed service with excellent integrations and a flexible architecture

Compared to any other tools, AWS products provide better integrations. We have tools for all our needs. The integrations are good. The product is a fully managed service. We specify the various stages in the CI/CD process. We can do it without any external tools. Going through everything is usually an overhead for developers. It is like a configuration. We need to configure it only once. The integration with other AWS services has helped us. Our life as a developer is easy. We need not focus on the integration manually. If we work with third-party tools, we must consider connectivity, role management, security, authentication, and authorization. In AWS CodePipeline, if we have IAM roles configured and KMS for the credentials, we need not worry about anything else. Everything can be done within the tool. The integrations are the best part. We can track everything. The connectivity and scalability are good. The architecture is also flexible enough. We can add multiple things.

Read full review

AllenUmlas

Engineer at Etisalat

Streamlines the CI/CD process with its user-friendly interface, extensive plugin ecosystem and efficient automation capabilities

Jenkins is incredibly user-friendly, so I haven't encountered any difficulties using it. It's the only product I've used for automation, but I find it to be very intuitive and effective. Jenkins has been instrumental in automating our build and deployment processes. We're leveraging Jenkins to automate tasks related to Telco, particularly in upgrading the manual orchestration. It's a critical tool for streamlining our operations.

Read full 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 a one-stop solution that you can use to integrate, deploy and host your application."

"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."

"The integrations are good."

"The management of CodeBuild and CodeDeploy on a three-point trigger basis is an important feature."

"It's a perfect solution if you are just using AWS."

"Another big advantage is observability."

"CodePipeline allows integration with any source code and facilitates deployment to EC2 or ECS, which is highly valuable."

More AWS CodePipeline pros

"Jenkins is particularly valuable since it saves time by automating manual tasks."

"The automated elements are easy to use and you can put them into your server."

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

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

"Jenkins is a CI/CD tool and is the most robust tool."

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

"Jenkins is very stable."

"Jenkins has a lot of built-in packages and tools."

More Jenkins pros

Cons

"One downside in AWS is that when you attempt to push a change in, it misses that part, or it could be because some variables are not set correctly."

"In AWS CodePipeline, we can only use certain tools for which AWS provisions plugins."

"The product’s pricing needs improvement."

"AWS CodePipeline is quite a simple tool mostly for management and creating automation."

"The migration process from one source code to another needs improvement."

"The support team’s response time must be improved."

"The tool does not provide automated features for evidence collection."

"There could be a possibility of deploying tag-based conditions for different environments using the same code base."

More AWS CodePipeline cons

"There are some issues with Jenkins, especially with the SIP job."

"Jenkins can sometimes run slow, especially when restarting after a plugin installation or when returning from a pipeline view to the dashboard."

"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."

"The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective."

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

"The documentation could be more friendly, and more examples of how to use it."

"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."

"I would like to see even more integrations included in the next release."

More Jenkins cons

Pricing and Cost Advice

"The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model."

"The pricing is manageable."

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

"It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."

"I would rate the product's pricing a five out of ten."

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

"The product is quite expensive compared to other solutions."

"AWS charges you based on the number of pipelines you have and how active they are, and I also think that the root account user knows about all the price-related metrics."

More AWS CodePipeline pricing and cost advice

"Some of the add-ons are too expensive."

"It is free."

"We are using the freeware version of Jenkins."

"The tool is open-source."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"It's free software with a big community behind it, which is very good."

"Jenkins is a free open-source server."

"There is no cost. It is open source."

More Jenkins pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

824,053 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

Jan 22, 2015

I generally find TeamCity a lot more intuitive than Jenkins.

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…

Read full review

Top Industries

By visitors reading reviews

Computer Software Company

17%

Financial Services Firm

15%

Government

Manufacturing Company

Financial Services Firm

23%

Computer Software Company

16%

Manufacturing Company

11%

Government

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

Questions from the Community

Which AWS solution would you choose - CodeStar or CodePipeline?

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

What do you like most about AWS CodePipeline?

Code deployment is the best feature.

What is your experience regarding pricing and costs for AWS CodePipeline?

AWS CodePipeline and its associated services do not incur significant additional charges. The cost primarily comes from deploying other AWS resources like EC2 and S3 alongside the pipeline.

How does Tekton compare with Jenkins?

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

What do you like most about Jenkins?

Jenkins has been instrumental in automating our build and deployment processes.

What is your experience regarding pricing and costs for Jenkins?

Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.

GitLab vs AWS CodePipeline

Comparisons

Compared 60% of the time

GitHub Actions vs AWS CodePipeline

Compared 12% of the time

AWS CodeStar vs AWS CodePipeline

Compared 6% of the time

Tekton vs AWS CodePipeline

Compared 5% of the time

Bamboo vs AWS CodePipeline

Compared 2% of the time

More AWS CodePipeline Competitors

GitLab vs Jenkins

Compared 16% of the time

Bamboo vs Jenkins

Compared 14% of the time

Harness vs Jenkins

Compared 11% of the time

Bazel vs Jenkins

Compared 9% of the time

Tekton vs Jenkins

Compared 7% of the time

More Jenkins Competitors

Product Reports

AWS CodePipeline

Download AWS CodePipeline product report

Download Jenkins product report

Also Known As

CodePipeline

No data available

Learn More

Amazon Web Services (AWS)

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

AWS CodePipeline vs. Jenkins