No more typing reviews! Try our Samantha, our new voice AI agent.

AWS CodeBuild 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 CodeBuild
Ranking in Build Automation
12th
Average Rating
8.2
Reviews Sentiment
6.4
Number of Reviews
13
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
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.3%, up from 1.2% compared to the previous year. The mindshare of Jenkins is 8.7%, down from 10.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Jenkins8.7%
AWS CodeBuild2.3%
Other89.0%
Build Automation
 

Featured Reviews

SomdipRoy - PeerSpot reviewer
Solution Architect at Skillnetinc
Has enabled automated deployments through continuous integration and supports multi-environment delivery
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as GitHub Actions, but it provides a very competitive price compared to GitHub Actions. GitHub Actions, if you want to use the YML CI/CD pipeline, gives a free tier of around three thousand hours per month. AWS CodeBuild is a little more expensive than that. However, if it supports the repository function as well along with it, then it will be a complete package. Everything would be in AWS, including the code versioning, code commit to the code infrastructure, to the code database, to the networking, and how the applications are accessed. Everything would be in one place, which would be very helpful. I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well. At the enterprise level, it charges maybe around nineteen dollars per user, though I do not remember exactly. In terms of AWS CodeBuild, I believe it is a bit expensive because it is providing only the deployment features. It is not providing the repository. In that comparison, I would say it is a little bit expensive.
Mahdi Mallaki - PeerSpot reviewer
Senior Devops Engineer at a tech vendor with 10,001+ employees
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

"CodeBuild supports various platforms and coding."
"The most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."
"The solution provides good integrations."
"One of the main features I value in CodeBuild compared to previous experiences, like using Jenkins, is its ability to handle tasks automatically with AWS, requiring only proper setup of the check file."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"CodeBuild supports various platforms and coding, which offers an advantage."
"The integration with other AWS services has streamlined our workflow."
"The integration is a good feature."
"Jenkins is stable, user-friendly, and helps with continuous integration."
"The most valuable feature of Jenkins is its continuous deployment, and we can deploy to multi-cluster and multi-regions in the cloud."
"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 automated elements are easy to use and you can put them into your server."
"The most valuable features I have found are it can integrate other services as a plugin."
"It is open source, flexible, scalable, and easy to use."
"Jenkins is very stable."
"The most valuable feature is its ability to connect with different tools and technologies."
 

Cons

"I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well."
"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"There is no persistent storage or preservation of workspace between the builds."
"They can further improve the integration of the Bitbucket for CodeBuild."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."
"I rate Jenkins two out of 10. If you think it's going to save you money because it's open source, think again."
"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."
"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."
"For this solution to be a 10, it has to be a lot more stable."
"Jenkins takes a long time to create archive files."
"It could be cheaper because there are many solutions available in the market."
"There is no way for the cloud repositories to trigger Jenkins."
"Occasional technical glitches after upgrades."
 

Pricing and Cost Advice

"Despite the cost, it is worth the investment."
"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."
"We pay a monthly licensing fee."
"Jenkins is open-source, so it is free."
"Jenkins is open source and free."
"Jenkins is a free open-source server."
"The solution is open source."
"Jenkins is an open-source platform."
"Jenkins is open source."
"In our company, we do pay for the licensing of the solution."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
896,202 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
10%
Media Company
9%
Computer Software Company
8%
Financial Services Firm
19%
Manufacturing Company
13%
Comms Service Provider
7%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise4
Large Enterprise2
By reviewers
Company SizeCount
Small Business27
Midsize Enterprise15
Large Enterprise58
 

Questions from the Community

What is your experience regarding pricing and costs for AWS CodeBuild?
The cost structure is affordable for most builds except macOS servers. Standard builds can utilize AWS EC2 servers for background operations. However, macOS or iOS builds require physical servers m...
What needs improvement with AWS CodeBuild?
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as G...
What is your primary use case for AWS CodeBuild?
My use of AWS CodeBuild is focused on the CI/CD part, which stands for continuous integration and continuous deployment. Basically, we write the code and then commit it into a repository, which cou...
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 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.
What needs improvement with Jenkins?
I do not have any notes for improvement.
 

Comparisons

 

Also Known As

CodeBuild
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 CodeBuild vs. Jenkins and other solutions. Updated: April 2026.
896,202 professionals have used our research since 2012.