AWS CodeBuild vs Jenkins comparison

Read 93 Jenkins reviews

4,766 Views
4,121 Comparison Views

87% willing to recommend

AWS CodeBuild

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between AWS CodeBuild and Jenkins based on real PeerSpot user reviews.

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.

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

AWS CodeBuild vs. Jenkins

Download the complete report

Helped 831,158 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

8th

Average Rating

8.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Jenkins

Ranking in Build Automation

3rd

Average Rating

8.0

Reviews Sentiment

6.9

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of January 2025, in the Build Automation category, the mindshare of AWS CodeBuild is 1.2%, down from 1.8% compared to the previous year. The mindshare of Jenkins is 11.3%, down from 14.3% 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 initial setup of CodeBuild is easy."

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

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

"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."

More AWS CodeBuild pros

"Jenkins is free and open source."

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

"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."

"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."

"Has enabled full automation of the company."

"Jenkins is very customizable."

"Having builds and test tasks triggered on commit helps not to break the product."

"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."

More Jenkins pros

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

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

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

"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 is no persistent storage or preservation of workspace between the builds."

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

More AWS CodeBuild cons

"It could be cheaper."

"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."

"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."

"The documentation on plugin development could be better: more examples. "

"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."

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

"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."

"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."

More Jenkins cons

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

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"It is a free product."

"Jenkins is open source."

"I used the free OSS version all the time. It was enough for all my needs."

"Jenkins is open source and free."

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

"Some of the add-ons are too expensive."

"The solution is one of the lowest costs compared to competitors."

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

831,158 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

23%

Financial Services Firm

11%

Media Company

10%

Manufacturing Company

Financial Services Firm

23%

Computer Software Company

16%

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

GitLab vs AWS CodeBuild

Compared 22% of the time

More AWS CodeBuild Competitors

GitLab vs Jenkins

Compared 16% of the time

Harness vs Jenkins

Compared 12% of the time

Bamboo vs Jenkins

Compared 12% of the time

Bazel vs Jenkins

Compared 9% of the time

GoCD 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

Learn More

Amazon Web Services (AWS)

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.

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