AWS CodeBuild vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
776 views|721 comparisons
Jenkins Logo
7,158 views|6,126 comparisons
Comparison Buyer's Guide
Executive Summary

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

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: March 2024).
765,386 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 is a good feature."

More AWS CodeBuild Pros →

"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud.""The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script.""Jenkins is very user-friendly.""It can scale easily.""The automated elements are easy to use and you can put them into your server.""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.""Jenkins' most valuable feature is Pipeline.""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."

More Jenkins Pros →

Cons
"There is no persistent storage or preservation of workspace between the builds.""They can further improve the integration of the Bitbucket for CodeBuild."

More AWS CodeBuild Cons →

"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on.""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 scriptwriting process could be improved in this solution in the future.""The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy.""Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do.""A more user-friendly UI for creating pipelines would be helpful.""There is no way for the cloud repositories to trigger Jenkins.""We need more licensed product integrations."

More Jenkins Cons →

Pricing and Cost Advice
  • "We pay a monthly licensing fee."
  • 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.
    765,386 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:The solution provides good integrations.
    Top Answer:The pricing is okay. Jenkins is not costly, but we must pay for the underlying infrastructure. The infrastructure is continuously there for the entire duration. In AWS CodeBuild, we don't have a… more »
    Top Answer: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… 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
    12th
    out of 41 in Build Automation
    Views
    776
    Comparisons
    721
    Reviews
    1
    Average Words per Review
    628
    Rating
    8.0
    2nd
    out of 41 in Build Automation
    Views
    7,158
    Comparisons
    6,126
    Reviews
    37
    Average Words per Review
    388
    Rating
    7.8
    Comparisons
    GitLab logo
    Compared 25% of the time.
    CircleCI logo
    Compared 17% of the time.
    GitHub Actions logo
    Compared 10% 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 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Microsoft Azure 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 Company24%
    Financial Services Firm10%
    Insurance Company6%
    Comms Service Provider6%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    VISITORS READING REVIEWS
    Small Business22%
    Midsize Enterprise17%
    Large Enterprise61%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    Build Automation
    March 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    AWS CodeBuild is ranked 12th in Build Automation with 2 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. AWS CodeBuild is rated 9.0, 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 Microsoft Azure.

    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.