AWS CodeBuild vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
786 views|725 comparisons
100% willing to recommend
Jenkins Logo
6,756 views|5,825 comparisons
88% willing to recommend
Comparison Buyer's Guide
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: May 2024).
771,170 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The solution provides good integrations.""The integration is a good feature.""The integration with other AWS services has streamlined our workflow.""It works seamlessly with AWS Elastic Container Registry (ECR).""The integration is a good feature."

More AWS CodeBuild Pros →

"Jenkins is very easy to use.""Very easy to understand for newcomers.""Jenkins's open-based framework is very valuable.""Jenkins has a lot of built-in packages and tools.""It is easy to use.""Jenkins is a very mature product.""The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script.""It can scale easily."

More Jenkins Pros →

Cons
"The deployment fails sometimes.""There is no persistent storage or preservation of workspace between the builds.""They can further improve the integration of the Bitbucket for CodeBuild.""While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."

More AWS CodeBuild Cons →

"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job.""It would be helpful if they had a bit more interactive UI.""There are some difficulties when we need to execute the DB script.""We need more licensed product integrations.""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.""Centralized user management would be helpful.""Jenkins relies on the old version of interface for configuration management. This needs improvement.""They need to improve their documentation."

More Jenkins Cons →

Pricing and Cost Advice
  • "We pay a monthly licensing fee."
  • "Despite the cost, it is worth the investment."
  • More AWS CodeBuild Pricing and Cost Advice →

  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,170 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    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 nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:It works seamlessly with AWS Elastic Container Registry (ECR).
    Top Answer:Using AWS CodeBuild might involve some initial expenses, but there are strategies to optimize costs and ensure a return on investment. Leveraging features like caching files and using the artifact… more »
    Top Answer:While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected. Although conditions were… more »
    Top Answer: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 easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    9th
    out of 41 in Build Automation
    Views
    786
    Comparisons
    725
    Reviews
    4
    Average Words per Review
    412
    Rating
    8.8
    2nd
    out of 41 in Build Automation
    Views
    6,756
    Comparisons
    5,825
    Reviews
    37
    Average Words per Review
    382
    Rating
    7.9
    Comparisons
    GitLab logo
    Compared 23% of the time.
    CircleCI logo
    Compared 15% of the time.
    GitHub Actions logo
    Compared 13% of the time.
    Tekton logo
    Compared 8% of the time.
    AWS CodePipeline logo
    Compared 6% of the time.
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 10% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    JFrog Pipeline logo
    Compared 3% of the time.
    Also Known As
    CodeBuild
    Learn More
    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
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company23%
    Financial Services Firm11%
    Insurance Company7%
    Government6%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    VISITORS READING REVIEWS
    Small Business21%
    Midsize Enterprise18%
    Large Enterprise61%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    AWS CodeBuild vs. Jenkins
    May 2024
    Find out what your peers are saying about AWS CodeBuild vs. Jenkins and other solutions. Updated: May 2024.
    771,170 professionals have used our research since 2012.

    AWS CodeBuild is ranked 9th in Build Automation with 4 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. AWS CodeBuild is rated 8.8, while Jenkins is rated 8.0. The top reviewer of AWS CodeBuild writes "Provides good integrations, is flexible, and has a comparable price". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". AWS CodeBuild is most compared with GitLab, CircleCI, GitHub Actions, Tekton and AWS CodePipeline, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and JFrog Pipeline. See our AWS CodeBuild vs. Jenkins report.

    See our list of best Build Automation vendors.

    We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.