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

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
9th
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
4th
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 February 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.2%, up from 1.2% compared to the previous year. The mindshare of Jenkins is 7.2%, down from 11.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Jenkins7.2%
AWS CodeBuild2.2%
Other90.6%
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.
JI
Principal Software Engineer at a financial services firm with 5,001-10,000 employees
Efficient resource allocation and robust workflow with autoscaling capabilities
In Kubernetes, we use node-based architecture with nodes and pods and follow practices like RBAC and rollback. Multiple pods can run concurrently. 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.

Quotes from Members

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

Pros

"It works seamlessly with AWS Elastic Container Registry (ECR)."
"CodeBuild supports various platforms and coding."
"AWS CodeBuild reduces wait time and optimizes workflows."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"The initial setup of CodeBuild is easy."
"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."
"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."
"AWS CodeBuild's support for a wide range of programming languages and build environments benefits development teams significantly in terms of productivity and ease of use."
"Jenkins is very easy to use."
"Jenkins's open-based framework is very valuable."
"Jenkins is very customizable."
"It's a powerful tool for CI/CD."
"The solution is scalable and concurrent users have access to the platform."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"Jenkins has built good plugins and has a good security platform."
"The deployment of traditional Jenkins is easy."
 

Cons

"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"There is no persistent storage or preservation of workspace between the builds."
"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."
"The deployment fails sometimes."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"They can further improve the integration of the Bitbucket for CodeBuild."
"For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs."
"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 bug fix speed is very slow."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Jenkins could improve the integration with other platforms."
"We cannot change the ownership of any directory or file or any kind of directory."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"It does not have a very user-friendly interface."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
 

Pricing and Cost Advice

"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."
"Despite the cost, it is worth the investment."
"We pay a monthly licensing fee."
"Jenkins is a free open-source server."
"Jenkins is open-source, so it is free."
"​It is free.​"
"Jenkins is open source."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"Jenkins is an open-source platform."
"The tool is open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
881,707 professionals have used our research since 2012.
 

Comparison Review

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

Top Industries

By visitors reading reviews
Computer Software Company
13%
Media Company
13%
Manufacturing Company
11%
Financial Services Firm
10%
Financial Services Firm
19%
Manufacturing Company
14%
Computer Software Company
9%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise5
Large Enterprise2
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise15
Large Enterprise56
 

Questions from the Community

What do you like most about AWS CodeBuild?
It works seamlessly with AWS Elastic Container Registry (ECR).
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...
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

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: February 2026.
881,707 professionals have used our research since 2012.