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
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 April 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 initial setup of CodeBuild is easy."
"CodeBuild supports various platforms and coding."
"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."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"AWS CodeBuild reduces wait time and optimizes workflows."
"CodeBuild supports various platforms and coding, which offers an advantage."
"The integration is a good feature."
"I like that you can find a wide range of plugins for Jenkins."
"Jenkins's open-based framework is very valuable."
"Jenkins is a great solution if you're looking at automation because it reduces manual work and improves performance."
"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, and you can just build one container in it and deploy it."
"Don't focus on the fact that Jenkins is open source."
"We chose this solution because it is in line with the budget and customer preferences."
"Jenkins automated the build and test portion of the CI/CD pipeline."
"It's very useful when you want to automate different processes from beginning to end."
 

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."
"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."
"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."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"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 documentation could be more friendly, and more examples of how to use it."
"Many of the plugins needs to be streamlined, their terminology needs to be the same and some plugins should be split into multiple smaller plugins."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Sometimes, random errors of metadata are not there, which causes delays."
"Jenkins can sometimes run slow, especially when restarting after a plugin installation or when returning from a pipeline view to the dashboard."
"The default settings do not work properly on Mac OS X."
"I would like to see more integrations included in the next release."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
 

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."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"Jenkins is a free open-source server."
"I used the free OSS version all the time. It was enough for all my needs."
"There is no cost. It is open source."
"Some of the add-ons are too expensive."
"The pricing for Jenkins is free."
"Jenkins is a free solution, it is open source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
885,667 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Media Company
10%
Financial Services Firm
10%
Manufacturing Company
10%
Healthcare Company
9%
Financial Services Firm
16%
Manufacturing Company
14%
Computer Software Company
8%
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 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: March 2026.
885,667 professionals have used our research since 2012.