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

AWS CodePipeline vs Jenkins comparison

 

Comparison Buyer's Guide

Executive Summary

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
4th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
22
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
93
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the Build Automation category, the mindshare of AWS CodePipeline is 6.1%, down from 9.0% compared to the previous year. The mindshare of Jenkins is 11.0%, down from 14.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Udhay Prakash Pethakamsetty - PeerSpot reviewer
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.
Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

Quotes from Members

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

Pros

"AWS CodePipeline has valuable integration features."
"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."
"CodePipeline allows integration with any source code and facilitates deployment to EC2 or ECS, which is highly valuable."
"The notification and approval approach in the production environment are very useful."
"AWS CodePipeline's most valuable feature is its seamless integration with other AWS services, making it easier to orchestrate deployment processes."
"The best thing about AWS CodePipeline is that we don't have to manage agents."
"The integration with other applications is fabulous."
"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."
"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."
"The most valuable feature of the solution is its integration between different tools."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"Having builds and test tasks triggered on commit helps not to break the product."
"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."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
 

Cons

"In AWS CodePipeline, we can only use certain tools for which AWS provisions plugins."
"It would be best if AWS CodePipeline provided multiple integration options directly by providing some URLs."
"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."
"The setup time is a bit long."
"If you're talking about multi-cloud, you can't use it."
"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."
"If there are many dependancies involved in the setup, it may take a long time."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"The solution's UI can use a facelift and the logs can use more detailed information."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"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."
"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
"The documentation could be more friendly, and more examples of how to use it."
"There are some issues with Jenkins, especially with the SIP job."
"The user interface could be updated a little."
 

Pricing and Cost Advice

"AWS offers free business or enterprise support services."
"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."
"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 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."
"It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
"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 free product."
"In our company, we do pay for the licensing of the solution."
"Some of the add-ons are too expensive."
"The solution is open source."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"Jenkins is open source and free."
"Jenkins is open source."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
838,640 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
Computer Software Company
16%
Financial Services Firm
14%
Government
8%
Manufacturing Company
6%
Financial Services Firm
22%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
 

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

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: January 2025.
838,640 professionals have used our research since 2012.