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 Market Share Distribution
ProductMarket Share (%)
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

"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 initial setup of CodeBuild is easy."
"The integration is a good feature."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"The integration is a good feature."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"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."
"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 initial setup is simple."
"The initial setup is pretty simple."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"Jenkins has been instrumental in automating our build and deployment processes."
"Having builds and test tasks triggered on commit helps not to break the product."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"It can scale easily."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
 

Cons

"Multiple clients have faced issues with pricing. After migrating from Azure to EC2, they were unexpectedly charged 100,000 rupees because the pricing details were not clearly visible."
"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"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."
"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."
"They can further improve the integration of the Bitbucket for CodeBuild."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"The upgrades need improvement."
"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."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
"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."
"There are some issues with Jenkins, especially with the SIP job."
"The user interface could be updated a little."
"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."
"The bug fix speed is very slow."
 

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."
"It's free software with a big community behind it, which is very good."
"Jenkins is an open-source platform."
"The pricing for Jenkins is free."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"Some of the add-ons are too expensive."
"Jenkins is a free open-source server."
"It is a free product."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
883,546 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
Media Company
13%
Manufacturing Company
11%
Computer Software Company
11%
Financial Services Firm
9%
Financial Services Firm
17%
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,546 professionals have used our research since 2012.