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
12th
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
7.0
Number of Reviews
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.3%, up from 1.2% compared to the previous year. The mindshare of Jenkins is 9.1%, down from 10.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Jenkins9.1%
AWS CodeBuild2.3%
Other88.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.
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 integration is a good feature."
"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."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"Scalability is a great feature with AWS CodeBuild, because after deploying applications the service automatically scales up and down according to our AWS needs using load balancing, which makes managing applications much easier without significant interruptions."
"The integration with other AWS services has streamlined our workflow."
"The initial setup of CodeBuild is easy."
"CodeBuild supports various platforms and coding, which offers an advantage."
"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."
"Jenkins is a scalable, open-source tool with multiple plugins that is easy to use and set up, and we can integrate it with multiple technologies, whether a .NET application or anything else."
"Don't focus on the fact that Jenkins is open source."
"The automated elements are easy to use and you can put them into your server."
"The most valuable feature of Jenkins is its continuous deployment, and we can deploy to multi-cluster and multi-regions in the cloud."
"Potential deployment problems pop up almost instantly during the development process, and the developers are more confident about their committed code."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"We use Jenkins for everything, empowering developers to have the confidence to deploy their solutions themselves into production instead of asking us as an operations guide."
 

Cons

"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"There is no persistent storage or preservation of workspace between the builds."
"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."
"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."
"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."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"The upgrades need improvement."
"The solution's UI can use a facelift and the logs can use more detailed information."
"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."
"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."
"One area for improvement would be the UI, which currently looks quite outdated and requires the user to go through too many steps."
"I would like to have an integrated dashboard on top of it and a better UX to look at."
"It does not have a very user-friendly interface."
 

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."
"Jenkins is open-source, so it is free."
"​It is free.​"
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"It is a free product."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"The pricing for Jenkins is free."
"It's free software with a big community behind it, which is very good."
"In our company, we do pay for the licensing of the solution."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
896,942 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Financial Services Firm
13%
Media Company
9%
Computer Software Company
8%
Financial Services Firm
19%
Manufacturing Company
13%
Computer Software Company
7%
Comms Service Provider
7%
 

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 Business27
Midsize Enterprise15
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?
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: April 2026.
896,942 professionals have used our research since 2012.