Need advice about which tool to choose?Ask the StackShare community!
AWS CodeBuild vs AWS CodePipeline: What are the differences?
AWS CodeBuild: Build and test code with continuous scaling. 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 CodePipeline: Continuous delivery service for fast and reliable application updates. CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
AWS CodeBuild can be classified as a tool in the "Continuous Integration" category, while AWS CodePipeline is grouped under "Continuous Deployment".
Some of the features offered by AWS CodeBuild are:
- Fully Managed Build Service
- Continuous Scaling
- Enables Continuous Integration
On the other hand, AWS CodePipeline provides the following key features:
- Workflow Modeling
- AWS Integrations
- Pre-Built Plugins
"Pay per minute" is the primary reason why developers consider AWS CodeBuild over the competitors, whereas "Simple to set up" was stated as the key factor in picking AWS CodePipeline.
Volta Industries, ChromaDex, and PouchNATION are some of the popular companies that use AWS CodePipeline, whereas AWS CodeBuild is used by Convox, Volta Industries, and ChromaDex. AWS CodePipeline has a broader approval, being mentioned in 30 company stacks & 15 developers stacks; compared to AWS CodeBuild, which is listed in 21 company stacks and 14 developer stacks.





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
.
Pros of AWS CodeBuild
- Pay per minute7
- Parameter Store integration for passing secrets5
- Integrated with AWS4
- Bit bucket integration3
- Streaming logs to Amazon CloudWatch3
- AWS Config and Config rule integration for compliance2
- GitHub Webhooks support2
- VPC PrivateLinks to invoke service without internet2
- Perpetual free tier option (100 mins/month)1
- Windows/.NET support1
- Jenkins plugin integration1
- Ondemand scaling of build jobs1
- Scheduled builds with CloudWatch Events integration1
- Local build debug support1
- Native support for accessing Amazon VPC resources1
- Docker based build environment1
- Support for bringing custom Docker images1
- Fully managed (no installation/updates, servers to mai1
- PCI, SOC, ISO, HIPAA compliant1
- Full API/SDKs/CLI support1
- YAML based configuration1
- Great support (forums, premium support, SO, GitHub)1
- GitHub Enterprise support1
- G0
Pros of AWS CodePipeline
- Simple to set up13
- Managed service8
- GitHub integration4
- Parallel Execution3
- Automatic deployment2
- Manual Steps Available0
Sign up to add or upvote prosMake informed product decisions
Cons of AWS CodeBuild
- Poor branch support1
Cons of AWS CodePipeline
- No project boards2
- No integration with "Power" 365 tools1