AWS CodeBuild vs Jenkins comparison

Read 93 Jenkins reviews

3,827 Views
2,496 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: June 2025).

AWS CodeBuild vs. Jenkins

Download the complete report

Helped 856,873 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

9th

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 June 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.5%, down from 13.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Munisaiteja Narravula

AWS Engineer at 6thgen

Automated task handling with reliable logging but requires accurate environment setup

One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors. It's crucial to have accurate environment configurations to avoid such problems. During the build stage, we often face time issues that cause delays, which can be troublesome.

Read full review

Mahdi Mallaki

Senior Devops Engineer at Rakuten

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.

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

"AWS CodeBuild reduces wait time and optimizes workflows."

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

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

"CodeBuild supports various platforms and coding."

"The integration is a good feature."

More AWS CodeBuild pros

"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."

"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."

"Distributed execution of build and test jobs."

"It's very easy to learn."

"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."

"A lot of support material exists via a single web search of exactly what you're looking for."

"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."

"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

"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."

"The deployment fails sometimes."

"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."

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

"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."

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

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

"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."

More AWS CodeBuild cons

"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."

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

"It can be improved by including automated mobile reporting integrations."

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

"There are some difficulties when we need to execute the DB script."

"It could be cheaper."

"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."

"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."

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 a free solution, it is open source."

"It is a cheap solution."

"Jenkins is open source."

"We are using the free version of Jenkins. There are no costs or licensing."

"There is no cost. It is open source."

"Jenkins is an open-source platform."

"Jenkins is an open-source tool."

"It is an open source."

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

856,873 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

17%

Financial Services Firm

13%

Manufacturing Company

11%

Media Company

10%

Financial Services Firm

22%

Computer Software Company

18%

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?

Issues with pricing have been mentioned, especially for new clients who might not realize the cost implications initially, such as leaving servers on for too long and incurring unexpectedly high bi...

What needs improvement with AWS CodeBuild?

There is room for improvement in making AWS CodeBuild available on Windows servers in the Mumbai region. Multiple clients have faced issues with pricing. After migrating from Azure ( /products/micr...

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 47% of the time

GitLab vs AWS CodeBuild

Compared 21% of the time

More AWS CodeBuild Competitors

Harness vs Jenkins

Compared 16% of the time

GitLab vs Jenkins

Compared 13% of the time

Bazel vs Jenkins

Compared 9% of the time

Tekton vs Jenkins

Compared 8% of the time

Digital.ai Release vs Jenkins

Compared 2% 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