Try our new research platform with insights from 80,000+ expert users

AWS CodePipeline vs Jenkins comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS CodePipeline
Ranking in Build Automation
5th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
23
Ranking in other categories
No ranking in other categories
Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the Build Automation category, the mindshare of AWS CodePipeline is 5.1%, down from 8.0% compared to the previous year. The mindshare of Jenkins is 10.5%, down from 12.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Istiyak Ahmed - PeerSpot reviewer
Streamlined deployment through excellent integration with a straightforward setup
Our primary use case for CodePipeline involves deploying the different services, such as hosting a website on ECS or EC2 and deploying source code on container services or EC2 instances. We configure the source code with remote repositories like GitHub or Bitbucket, build the code, and store images…
Annamalai Pts - PeerSpot reviewer
Streamlined CI/CD pipelines with powerful integration and an easy setup
I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS Jenkins has made the developers' work very easy. They commit to the remote repository, and…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"AWS CodePipeline's most valuable feature is its seamless integration with other AWS services, making it easier to orchestrate deployment processes."
"Different applications can be enhanced with AWS CodePipeline"
"The integrations are good."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"The solution's technical support responds whenever you have an issue, especially whenever you need something sorted out from their side."
"I prefer using CodePipeline and CodeBuild in AWS due to their integration with AWS services, like directly deploying to ECS using Cloud Deploy."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
"The deployment of traditional Jenkins is easy."
"It's a powerful tool for CI/CD."
"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."
"This is a great integration tool and very powerful."
"Jenkins is particularly valuable since it saves time by automating manual tasks."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
 

Cons

"From my perspective, some in-built capabilities could be enhanced."
"The documentation for AWS CodePipeline is lacking and makes it difficult to find information due to its complexity. It would be helpful to have examples in the documentation for different project types like Laravel or Django."
"AWS CodePipeline functions well, but there's room for improvement in providing technical support to regular customers who haven't purchased developer support. I mean, having it available for everyone, even if it's not a 24-hour service. It would be more useful if specific support hours were available for assistance."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"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 AWS CodePipeline, we can only use certain tools for which AWS provisions plugins."
"The tool does not provide automated features for evidence collection."
"While CodePipeline's UI has improved, further enhancements in user experience are necessary to make it more intuitive."
"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."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
"The learning curve is quite steep at the moment."
"The user interface could be updated a little."
"The support for the latest Java Runtime Environment should be improved."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
 

Pricing and Cost Advice

"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."
"The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model."
"It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
"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."
"AWS offers free business or enterprise support services."
"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 pricing is manageable."
"The pricing for Jenkins is free."
"Jenkins is open source."
"Jenkins is an open-source tool."
"Jenkins is an open-source platform."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"Some of the add-ons are too expensive."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"It's free software with a big community behind it, which is very good."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
861,803 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
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…
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Government
8%
Manufacturing Company
6%
Financial Services Firm
22%
Computer Software Company
16%
Manufacturing Company
12%
Government
7%
 

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 is your experience regarding pricing and costs for AWS CodePipeline?
AWS CodePipeline's pricing is reasonable, and it is not too expensive. I estimated it costs around $5 monthly. On a scale from one to ten, where one is very cheap and ten is very expensive, I would...
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.
 

Comparisons

 

Also Known As

CodePipeline
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Find out what your peers are saying about AWS CodePipeline vs. Jenkins and other solutions. Updated: July 2025.
861,803 professionals have used our research since 2012.