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.
AllenUmlas - PeerSpot reviewer
Engineer at Etisalat
Streamlines the CI/CD process with its user-friendly interface, extensive plugin ecosystem and efficient automation capabilities
Jenkins is incredibly user-friendly, so I haven't encountered any difficulties using it. It's the only product I've used for automation, but I find it to be very intuitive and effective. Jenkins has been instrumental in automating our build and deployment processes. We're leveraging Jenkins to automate tasks related to Telco, particularly in upgrading the manual orchestration. It's a critical tool for streamlining our operations.

Quotes from Members

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

Pros

"AWS CodeBuild's support for popular languages and tools has enhanced my productivity; it supports the three most popular stacks that are in the world: the Python stack, the Node.js stack or framework, and the Java framework, along with other technology stacks such as Ruby on Rails."
"The integration is a good feature."
"The solution provides good integrations."
"The tool is used to build and test code. I find its biggest advantages are elasticity and reliability. We can easily assign as many computing resources as needed to build our code, which is much simpler than traditional methods that require server upgrades. It's a serverless tool, so it's very flexible and elastic."
"AWS CodeBuild reduces wait time and optimizes workflows."
"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."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"The solution is scalable and concurrent users have access to the platform."
"It's a powerful tool for CI/CD."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"Has enabled full automation of the company."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."
 

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."
"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."
"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."
"There is no persistent storage or preservation of workspace between the builds."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"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."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"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."
"The UI must be more user-friendly."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"Some kind of SaaS product would be helpful in providing organizational structure."
"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."
"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
 

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 open-source, so it is free."
"It is a free product."
"The tool is open-source."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."
"The solution is open source."
"Jenkins is not expensive and reasonably priced."
"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.
882,637 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
18%
Manufacturing Company
14%
Computer Software Company
9%
Government
7%
 

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 Enterprise57
 

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.
882,637 professionals have used our research since 2012.