No more typing reviews! Try our Samantha, our new voice AI agent.

AWS CodeBuild vs Jenkins comparison

Why PeerSpot?
 

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
10th
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
1st
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
93
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.3%, up from 1.8% compared to the previous year. The mindshare of Jenkins is 10.7%, up from 8.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Jenkins10.7%
AWS CodeBuild2.3%
Other87.0%
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.
HG
Cloud Architect at a outsourcing company with 51-200 employees
Automated pipelines have halved deployment time and allow developers to focus only on coding
The best features that Jenkins offers me are high customizability along with the support of Groovy language, which allows me to write my own functions and logic to deploy applications and configure the pipeline according to my use case. Its high integration capability with many plugins is also a significant advantage. For example, we have certain cloud functions running on Google Cloud Run, and we deploy those in the form of containers. Jenkins is highly integratable with Docker through plugins, so we installed those plugins in Jenkins and provided the credentials and logic for execution. Additionally, we have a Bitbucket environment and AWS deployments where we also use Jenkins' strong AWS plugins to deploy resources effectively. Thanks to these plugins, it's easy to deploy rather than creating custom logic. I have covered pretty much everything about the features of Jenkins.

Quotes from Members

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

Pros

"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 a wide range of programming languages and build environments benefits development teams significantly in terms of productivity and ease of use."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The initial setup of CodeBuild is easy."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"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 integration with other AWS services has streamlined our workflow."
"Jenkins has built good plugins and has a good security platform."
"The most valuable aspect of this solution is that there are multiple features, as we can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
"Has a good interface, is reliable and saves time."
"Jenkins is a great tool for continuous integration."
"The deploying and assessing of the development of our code and our application has been really useful, it's getting a bit easier for us to use Jenkins, and it is really helping us."
"There is a cost saving by using Jenkins because instead, we do not have to depend on the public cloud or any private cloud CI tools."
"Jenkins is free and open source."
"We have branches in Egypt and branches in Dubai that are using Jenkins for the whole automation process and we're really enjoying using it."
 

Cons

"They can further improve the integration of the Bitbucket for CodeBuild."
"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."
"There is no persistent storage or preservation of workspace between the builds."
"The servers used for macOS and iOS builds are limited in availability, operating only in US East 1 and East 2, and US West 1 and West 2. This geographical limitation causes latency issues and extended build times for regions such as India, impacting production efficiency."
"The deployment fails sometimes."
"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."
"Better and easy-to-use integration with Docker would be an improvement."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"Centralized user management would be helpful."
"The bug fix speed is very slow."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."
"There are some issues with Jenkins, especially with the SIP job."
"The enterprise version is less stable than the open-source version."
 

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."
"We pay a monthly licensing fee."
"Despite the cost, it is worth the investment."
"Jenkins is open-source, so it is free."
"In our company, we do pay for the licensing of the solution."
"The solution is open source."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"Jenkins is open source and free."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"It is an open source."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
920,929 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
14%
Outsourcing Company
12%
Comms Service Provider
8%
Financial Services Firm
8%
Financial Services Firm
15%
Manufacturing Company
13%
Outsourcing Company
10%
Comms Service Provider
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise4
Large Enterprise2
By reviewers
Company SizeCount
Small Business29
Midsize Enterprise14
Large Enterprise58
 

Questions from the Community

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...
What is your primary use case for AWS CodeBuild?
My use of AWS CodeBuild is focused on the CI/CD part, which stands for continuous integration and continuous deployment. Basically, we write the code and then commit it into a repository, which cou...
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?
We are using a community version of Jenkins and did not purchase it through the AWS Marketplace. The main cost for using Jenkins is related to the server it is hosted on and the allocated capacity....
What needs improvement with Jenkins?
Jenkins has many outdated plugins, and several are paid, which can be unnecessary. Better plugin maintainability is needed, and given the AI advancements today, AI support in Jenkins would be benef...
 

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: November 2026.
920,929 professionals have used our research since 2012.