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…
Mahdi Mallaki - PeerSpot reviewer
Has a community of plugin providers but needs improvement in Kubernetes integration
Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests. In contrast, GitLab offers an integrated Git repository and pipeline runner, streamlining the process. One improvement for Jenkins could be integrating a Git server, simplifying the management of CI/CD pipelines. Currently, with Jenkins, modifying pipeline manifests requires navigating to a separate Git repository. In GitLab, however, manifest changes can be made directly within the repository.

Quotes from Members

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

Pros

"The solution's technical support responds whenever you have an issue, especially whenever you need something sorted out from their side."
"AWS CodePipeline has valuable integration features."
"The management of CodeBuild and CodeDeploy on a three-point trigger basis is an important feature."
"The product is cost-effective and integrates well with the AWS environment."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"CodePipeline allows integration with any source code and facilitates deployment to EC2 or ECS, which is highly valuable."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"Jenkins' most valuable feature is Pipeline."
"We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load."
"The deployment of traditional Jenkins is easy."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"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."
"Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."
"The most valuable feature of Jenkins is its open source."
"Jenkins is a very mature product."
 

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."
"Improved enhancements and features could make it more intuitive."
"It would be best if AWS CodePipeline provided multiple integration options directly by providing some URLs."
"The tool does not provide automated features for evidence collection."
"If there are many dependancies involved in the setup, it may take a long time."
"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 setup time is a bit long."
"If you're talking about multi-cloud, you can't use it."
"Sometimes you have Jenkins restarting because of OOM errors."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."
"They need to improve their documentation."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
"The scriptwriting process could be improved in this solution in the future."
"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

"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."
"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."
"AWS offers free business or enterprise support services."
"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."
"It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
"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."
"I would rate the product's pricing a five out of ten."
"Jenkins is a free open-source server."
"We are using the free version of Jenkins. There are no costs or licensing."
"The solution is open source."
"​It is free.​"
"We are using the freeware version of Jenkins."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"It is an open source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
860,168 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
21%
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: June 2025.
860,168 professionals have used our research since 2012.