AWS CodeBuild vs AWS CodeDeploy

Overview

AWS CodeDeploy

Stacks380

Followers624

Votes38

AWS CodeBuild

Stacks443

Followers485

Votes43

AWS CodeBuild vs AWS CodeDeploy: What are the differences?

AWS CodeBuild and AWS CodeDeploy are two popular services provided by Amazon Web Services (AWS) that serve different purposes in the software development and deployment process. Here are the key differences between them.

Purpose: AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces ready-to-deploy software packages. It is primarily used to build and test code as part of the continuous integration and continuous delivery (CI/CD) process. On the other hand, AWS CodeDeploy is a fully managed deployment service that automates the deployment of applications to a variety of compute services such as Amazon EC2 instances, Lambda functions, and ECS tasks. It focuses on the deployment aspect of the software development lifecycle.
Build and Deployment Process: CodeBuild is primarily used for build and test processes. It can be triggered by events such as code commits to a version control repository, allowing developers to automate the build process whenever changes are made to the source code. CodeDeploy, on the other hand, takes over after the build process is complete and focuses on deploying the built artifacts to the target environment. It provides control over the deployment lifecycle, allowing for blue-green deployments, in-place deployments, and other deployment strategies.
Supported Platforms: CodeBuild supports a wide range of programming languages, build tools, and operating systems. It provides a flexible environment for building and testing code across various platforms. CodeDeploy, on the other hand, supports a variety of compute services such as EC2 instances, Lambda functions, and ECS tasks. It provides the ability to deploy applications to these services, making it suitable for diverse deployment scenarios.
Deployment Strategies: CodeBuild does not provide built-in deployment strategies and focuses solely on the build and test processes. On the other hand, CodeDeploy offers a range of deployment strategies such as blue-green deployments, canary deployments, and in-place deployments. These deployment strategies enable organizations to minimize downtime and gradually roll out changes to their applications.
Integration and Third-party Tools: CodeBuild integrates well with version control systems like AWS CodeCommit, GitHub, and Bitbucket, allowing it to trigger builds on code changes. It can also be integrated with other AWS services like AWS CodePipeline and AWS CloudFormation. CodeDeploy also integrates with CodePipeline, making it easier to create end-to-end CI/CD pipelines. Additionally, CodeDeploy provides integration with third-party tools like Jenkins, TeamCity, and Octopus Deploy, allowing organizations to leverage their existing deployment tools.
Pricing Structure: CodeBuild is priced based on the number of build minutes used, and the type and size of the compute environment used for building. CodeDeploy, on the other hand, is priced based on the number of instances deployed, making it suitable for organizations that have a large number of instances to manage.

In summary, AWS CodeBuild is primarily used for building and testing code, while AWS CodeDeploy focuses on the deployment aspect of software development. CodeBuild supports a wide range of programming languages and build tools, while CodeDeploy supports various compute services for deployment. CodeDeploy provides flexible deployment strategies, integration with third-party tools, and pricing based on the number of deployed instances.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on AWS CodeDeploy, AWS CodeBuild

Arthur

DevOps Engineer at DCSIL

Feb 6, 2020

Needs advice

We will use AWS CloudFormation, as it is ideal for deploying and replicating infrastructure as code. Amazon CloudWatch Events will be used to send info based on the trigger that initiated the event to developers using Amazon SNS. Amazon SNS will also be used in the AWS CodePipeline after the application has been tested and deployed successfully to the development environment, notifying users to approve the application before it can be deployed to a production environment. AWS CodeBuild will be used for running tests on the application and AWS CodeDeploy will be used to deploy the application to Lambda and Alexa Skills Kit. AWS CodePipeline is a service that will organize the steps taken (building/testing and deployment) when code is pushed to the master branch in our source repository in Github.

50.4k views50.4k

Comments

Detailed Comparison

AWS CodeDeploy	AWS CodeBuild
AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications.	AWS CodeBuild is a fully managed build 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.
AWS CodeDeploy fully automates your code deployments, allowing you to deploy reliably and rapidly;AWS CodeDeploy helps maximize your application availability by performing rolling updates across your Amazon EC2 instances and tracking application health according to configurable rules;AWS CodeDeploy allows you to easily launch and track the status of your deployments through the AWS Management Console or the AWS CLI;AWS CodeDeploy is platform and language agnostic and works with any application. You can easily reuse your existing setup code	Fully Managed Build Service;Continuous Scaling;Enables Continuous Integration;Integrates seamlessly with AWS services;FAQs: https://aws.amazon.com/codebuild/faqs/
Statistics
Stacks 380	Stacks 443
Followers 624	Followers 485
Votes 38	Votes 43
Pros & Cons
Pros 17 Automates code deployments 9 Backed by Amazon 7 Adds autoscaling lifecycle hooks 5 Git integration	Pros 7 Pay per minute 5 Parameter Store integration for passing secrets 4 Integrated with AWS 3 Bit bucket integration 3 Streaming logs to Amazon CloudWatch Cons 2 Poor branch support
Integrations
CircleCI Codeship GitHub Jenkins Solano CI Travis CI Amazon EC2 Ansible Chef Puppet Labs	AWS Elastic Beanstalk AWS CodeCommit Amazon S3 GitHub Bitbucket AWS CloudFormation Jenkins GitHub Enterprise

What are some alternatives to AWS CodeDeploy, AWS CodeBuild?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Octopus Deploy

Octopus Deploy helps teams to manage releases, automate deployments, and operate applications with automated runbooks. It's free for small teams.

Related Comparisons

AWS CodeBuild vs AWS CodeDeploy: What are the differences?

Purpose: AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces ready-to-deploy software packages. It is primarily used to build and test code as part of the continuous integration and continuous delivery (CI/CD) process. On the other hand, AWS CodeDeploy is a fully managed deployment service that automates the deployment of applications to a variety of compute services such as Amazon EC2 instances, Lambda functions, and ECS tasks. It focuses on the deployment aspect of the software development lifecycle.
Build and Deployment Process: CodeBuild is primarily used for build and test processes. It can be triggered by events such as code commits to a version control repository, allowing developers to automate the build process whenever changes are made to the source code. CodeDeploy, on the other hand, takes over after the build process is complete and focuses on deploying the built artifacts to the target environment. It provides control over the deployment lifecycle, allowing for blue-green deployments, in-place deployments, and other deployment strategies.
Supported Platforms: CodeBuild supports a wide range of programming languages, build tools, and operating systems. It provides a flexible environment for building and testing code across various platforms. CodeDeploy, on the other hand, supports a variety of compute services such as EC2 instances, Lambda functions, and ECS tasks. It provides the ability to deploy applications to these services, making it suitable for diverse deployment scenarios.
Deployment Strategies: CodeBuild does not provide built-in deployment strategies and focuses solely on the build and test processes. On the other hand, CodeDeploy offers a range of deployment strategies such as blue-green deployments, canary deployments, and in-place deployments. These deployment strategies enable organizations to minimize downtime and gradually roll out changes to their applications.
Integration and Third-party Tools: CodeBuild integrates well with version control systems like AWS CodeCommit, GitHub, and Bitbucket, allowing it to trigger builds on code changes. It can also be integrated with other AWS services like AWS CodePipeline and AWS CloudFormation. CodeDeploy also integrates with CodePipeline, making it easier to create end-to-end CI/CD pipelines. Additionally, CodeDeploy provides integration with third-party tools like Jenkins, TeamCity, and Octopus Deploy, allowing organizations to leverage their existing deployment tools.
Pricing Structure: CodeBuild is priced based on the number of build minutes used, and the type and size of the compute environment used for building. CodeDeploy, on the other hand, is priced based on the number of instances deployed, making it suitable for organizations that have a large number of instances to manage.

AWS CodeBuild vs AWS CodeDeploy

Overview