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 March 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.4%, up from 1.2% compared to the previous year. The mindshare of Jenkins is 7.3%, down from 10.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Jenkins7.3%
AWS CodeBuild2.4%
Other90.3%
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

"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."
"The integration with other AWS services has streamlined our workflow."
"The integration is a good feature."
"The initial setup of CodeBuild is easy."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"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."
"The integration is a good feature."
"CodeBuild supports various platforms and coding."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"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."
"Jenkins is very easy to use."
"Having builds and test tasks triggered on commit helps not to break the product."
"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."
"The most valuable feature of the solution is its integration between different tools."
"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."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
 

Cons

"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."
"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"They can further improve the integration of the Bitbucket for CodeBuild."
"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."
"There is no persistent storage or preservation of workspace between the builds."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."
"Sometimes you have Jenkins restarting because of OOM errors."
"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."
"The UI of Jenkins could improve."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"There are some difficulties when we need to execute the DB script."
"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."
"There are some issues with Jenkins, especially with the SIP job."
 

Pricing and Cost Advice

"We pay a monthly licensing fee."
"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."
"The solution is one of the lowest costs compared to competitors."
"Jenkins is open source and free."
"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 pricing for Jenkins is free."
"​It is free.​"
"It is an open source."
"There is no cost. It is open source."
"It is a free product."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
883,896 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
Manufacturing Company
11%
Computer Software Company
11%
Media Company
11%
Financial Services Firm
11%
Financial Services Firm
18%
Manufacturing Company
15%
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 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: March 2026.
883,896 professionals have used our research since 2012.