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

AWS CodeBuild vs CloudBees comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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
CloudBees
Ranking in Build Automation
15th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
20
Ranking in other categories
Configuration Management (17th), Value Stream Management Software (6th), DevSecOps (12th), AI-Augmented Software-Testing Tools (5th), Feature Management (3rd), AI Software Development (30th)
 

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 CloudBees is 3.3%, up from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
AWS CodeBuild2.3%
CloudBees3.3%
Other94.4%
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.
KishoreKumar4 - PeerSpot reviewer
Senior Qe Lead at Cognizant
Consistent automation has improved deployments and supports efficient client-facing workflows
Deployment and other processes are feasible for me, making this a smooth process. The integration part is good. We can use multiple things by integrating with CI/CD pipelines, and this is very feasible for us. This allows us to do our work easily. The productivity is very good. CloudBees is a good and efficient tool. We can work in client-facing scenarios, and since clients have provided these types of tools, we are able to work on them effectively.

Quotes from Members

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

Pros

"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."
"AWS CodeBuild reduces wait time and optimizes workflows."
"The solution provides good integrations."
"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."
"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 most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."
"CloudBees operates seamlessly. Deploying to a cluster is straightforward—just one click, and the job is done."
"The customer support is good. You get good representatives from CloudBees to help you and understand your requirements."
"The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."
"CloudBees updates its features frequently, so if we need something like SSL login, they enable it."
"Scalability largely depends on how the tool is set up within your infrastructure"
"The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar, management master to CloudBees, Blue Ocean, JobConfig, and support."
"CloudBees is a user-friendly tool."
"It’s a very good tool for auditing your project pipelines as well."
 

Cons

"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."
"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."
"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."
"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."
"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"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."
"One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time."
"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it."
"For CloudBees, I can suggest that the log is very high, which is very hectic for us when trying to find which error is coming."
"I would like to see improved speed and availability."
"We did face some challenges, particularly with the infrastructure."
"The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times."
"It could improve the document upload process."
 

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."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
14%
Outsourcing Company
12%
Financial Services Firm
8%
Comms Service Provider
8%
Construction Company
18%
Manufacturing Company
15%
Financial Services Firm
13%
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 Business2
Midsize Enterprise2
Large Enterprise18
 

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...
What needs improvement with CloudBees?
For CloudBees, I can suggest that the log is very high, which is very hectic for us when trying to find which error is coming. This creates complexity. If possible, we could sort the logs so we can...
What is your primary use case for CloudBees?
We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.
What advice do you have for others considering CloudBees?
We can upload the JAR file and deploy at the Jenkins level during our deployment. These types of labels and IDs can be deployed using CloudBees. Once we click to start the build, it automatically r...
 

Comparisons

 

Also Known As

CodeBuild
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Find out what your peers are saying about AWS CodeBuild vs. CloudBees and other solutions. Updated: November 2026.
920,769 professionals have used our research since 2012.