Try our new research platform with insights from 80,000+ expert users

AWS CodeBuild vs CloudBees 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
11
Ranking in other categories
No ranking in other categories
CloudBees
Ranking in Build Automation
7th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
20
Ranking in other categories
Configuration Management (11th), Value Stream Management Software (3rd), DevSecOps (5th)
 

Mindshare comparison

As of May 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 CloudBees is 1.2%, up from 0.1% 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.
YashBrahmani - PeerSpot reviewer
Offers a clear visualization and overview of workflows and helpful in managing CI/CD processes
Improvement in the sense that they can do better in terms of management of logs and stuff like that because the console logs are very extensive, and that causes a lot of storage issues. That is one of the things which is there. Also, with respect to the traditional platform and the modern platform, many things have upgraded, and it has quite improved. But when we talk about the performance of the agents, it’s still very crucial because it’s not up to par. It takes a lot of time to provision the agent and to finish the build because of the SSH connection and the JNLP connection. Due to that, sometimes the agent doesn’t get provisioned. Those are some of the blockers that meet up the time in terms of administering the instance.

Quotes from Members

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

Pros

"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."
"CodeBuild supports various platforms and coding."
"The integration is a good feature."
"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."
"The solution provides good integrations."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration is a good feature."
"The initial setup of CodeBuild is easy."
"The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."
"It can manage multiple Jenkins instances."
"CloudBees is a user-friendly tool."
"It’s a very good tool for auditing your project pipelines as well."
"The most valuable feature of the solution is that its GUI is quite simple."
"CloudBees's user interface is very simple and user-friendly."
"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."
 

Cons

"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 deployment fails sometimes."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"They can further improve the integration of the Bitbucket for CodeBuild."
"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"There is no persistent storage or preservation of workspace between the builds."
"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."
"Sometimes, there are performance issues, however, they may be due to our organization's configuration."
"I think a preview of the errors would be good just at the point where the error occurs."
"A lot of stability issues are there with CloudBees."
"I would like to see improved speed and availability."
"If you're logged in and working for about thirty minutes and then go idle for five to ten minutes, Jenkins will prompt you to re-authenticate."
"There could be improvements in the ease of use."
"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"To improve efficiency, they should focus on smoother label deployment."
 

Pricing and Cost Advice

"Despite the cost, it is worth the investment."
"We pay a monthly licensing fee."
"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."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
14%
Manufacturing Company
11%
Media Company
10%
Financial Services Firm
26%
Manufacturing Company
12%
Legal Firm
11%
Computer Software Company
9%
 

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.
What needs improvement with CloudBees?
There are connection issues with CloudBees, specifically between Sybase and CloudBees. We often encounter connection problems, and there are issues with the pipelines.
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?
I would recommend CloudBees to others because building jobs is much easier than with other solutions.
 

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: April 2025.
850,028 professionals have used our research since 2012.