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
11th
Average Rating
8.2
Reviews Sentiment
7.7
Number of Reviews
10
Ranking in other categories
No ranking in other categories
Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of AWS CodeBuild is 1.2%, down from 1.5% compared to the previous year. The mindshare of Jenkins is 10.4%, down from 13.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Udhay Prakash Pethakamsetty - PeerSpot reviewer
Provides good integrations, is flexible, and has a comparable price
The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the storage volumes. If we use S3 buckets regularly, it is fine. However, when we store somewhere else, it will be an issue. There is no persistent storage or preservation of workspace between the builds. We must fix the dependencies every time, even if the dependencies are the same. It is unnecessary.
Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

Quotes from Members

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

Pros

"The integration with other AWS services has streamlined our workflow."
"The integration is a good feature."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"The solution provides good integrations."
"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."
"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."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"This is a great integration tool and very powerful."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"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 aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
 

Cons

"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."
"They can further improve the integration of the Bitbucket for CodeBuild."
"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."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"There is no persistent storage or preservation of workspace between the builds."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"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 UI of Jenkins could improve."
"It can be improved by including automated mobile reporting integrations."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"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."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"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."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
 

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."
"Despite the cost, it is worth the investment."
"We pay a monthly licensing fee."
"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"I used the free OSS version all the time. It was enough for all my needs."
"Jenkins is open source."
"It is a free product."
"It is a cheap solution."
"Jenkins is not expensive and reasonably priced."
"There is no cost. It is open source."
"We are using the free version of Jenkins. There are no costs or licensing."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
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
Computer Software Company
21%
Financial Services Firm
13%
Manufacturing Company
12%
Media Company
9%
Financial Services Firm
22%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
Regarding pricing, AWS services are quite expensive compared to open source tools like Git that are available for free.
What needs improvement with AWS 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.
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 2025.
845,040 professionals have used our research since 2012.