AWS CodeBuild vs Jenkins comparison

Read 93 Jenkins reviews

4,156 Views
3,557 Comparison Views

87% willing to recommend

AWS CodeBuild

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Mar 5, 2025

Jenkins and AWS CodeBuild are prominent players in the CI/CD space. While Jenkins offers extensive customization and flexibility through its open-source nature, AWS CodeBuild gains an edge with seamless AWS service integration and effortless scalability.

Features: Jenkins provides a robust ecosystem with extensive plugin support, including Jenkins Pipelines, which allows for high pipeline customization, and programmable pipelines for process automation. AWS CodeBuild offers native integration with AWS services, serverless architecture that enhances elasticity and reliability, and seamless integration with third-party tools such as GitHub, facilitating ease of use within AWS environments.

Room for Improvement: Jenkins could enhance its installation process across different platforms, address plugin management issues, and update its interface for a better user experience. AWS CodeBuild may improve by strengthening integration with external storage solutions, enhancing loop functionality within scripts, and developing a more intuitive user interface along with improved build notification features.

Ease of Deployment and Customer Service: Jenkins supports on-premises, hybrid, and cloud deployments, but lacks formal customer service, relying on community support. AWS CodeBuild focuses on managed public cloud deployment, reducing infrastructure concerns for AWS users and offering AWS support that minimizes the need for community reliance.

Pricing and ROI: Jenkins is an open-source tool with no license fees, making it highly cost-effective for organizations seeking community support. AWS CodeBuild's pay-as-you-go pricing based on compute resources provides financial flexibility, though it may be more expensive than Jenkins. Jenkins could lead to substantial cost savings in large deployments, while AWS CodeBuild offers competitive pricing and reasonable ROI, especially for projects already integrated into AWS.

To learn more, read our detailed AWS CodeBuild vs. Jenkins Report (Updated: March 2025).

AWS CodeBuild vs. Jenkins

Download the complete report

Helped 845,040 peers since 2012

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

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

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

Data Engineer Manager at Capgemini

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.

Read full review

Dinesh-Patil

Consultant at a manufacturing company with 10,001+ employees

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.

Read full review

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 solution provides good integrations."

"CodeBuild supports various platforms and coding."

"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 integration with other AWS services has streamlined our workflow."

"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."

"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."

More AWS CodeBuild pros

"When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."

"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."

"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."

"It offers continuous deployment and continuous testing. It enables us to figure out anything."

"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."

"The solution is scalable and has a large number of plugins that can help you scale it to your needs."

"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."

"We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load."

More Jenkins pros

Cons

"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."

"There is no persistent storage or preservation of workspace between the builds."

"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."

"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."

"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."

"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 front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."

More AWS CodeBuild cons

"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."

"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."

"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."

"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."

"Better and easy-to-use integration with Docker would be an improvement."

"Jenkins needs a faster deployment process."

"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."

"Some kind of SaaS product would be helpful in providing organizational structure."

More Jenkins cons

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."

"Jenkins is open source."

"It is a cheap solution."

"Jenkins is a free open-source server."

"The solution is open source."

"It is a free product."

"In our company, we do pay for the licensing of the solution."

"It is free."

"Jenkins is open-source, so it is free."

More Jenkins pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

845,040 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

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…

Read full review

Top Industries

By visitors reading reviews

Computer Software Company

21%

Financial Services Firm

13%

Manufacturing Company

12%

Media Company

Financial Services Firm

22%

Computer Software Company

17%

Manufacturing Company

11%

Government

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.

GitHub Actions vs AWS CodeBuild

Comparisons

Compared 43% of the time

GitLab vs AWS CodeBuild

Compared 19% of the time

More AWS CodeBuild Competitors

GitLab vs Jenkins

Compared 15% of the time

Harness vs Jenkins

Compared 14% of the time

Bazel vs Jenkins

Compared 9% of the time

Bamboo vs Jenkins

Compared 9% of the time

CircleCI vs Jenkins

Compared 3% of the time

More Jenkins Competitors

Product Reports

AWS CodeBuild

Download AWS CodeBuild product report

Download Jenkins product report

Also Known As

CodeBuild

No data available

Overview

AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers. CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue. You can get started quickly by using prepackaged build environments, or you can create custom build environments that use your own build tools. With CodeBuild, you are charged by the minute for the compute resources you use.

Amazon Web Services (AWS)

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox

AWS CodeBuild vs. Jenkins