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.
What is AWS CodeBuild?
What is AWS CodePipeline?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using AWS CodeBuild?
What are the cons of using AWS CodePipeline?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The open-source Convox Platform-as-a-Service is built entirely on AWS cloud services.
Through this lens, it's been obvious that AWS has been missing a managed build service. For the past year we've had to work around this by building our own build service on ECS and ECR. You can read more on my AWS Missing Parts: Build Service blog post.
So I'm excited to finally have this service. After a quick weekend prototype, the service works as expected and will unlock Cheaper, Faster and Safer Builds for our systems.
This is a classic AWS service. It's tricky to figure out all the options. I recommend jumping straight to the Docker example docs:
You'll need to figure IAM, Build Project JSON, and Build Spec YAML to get it all working.
But once you do, you've unlocked managed builds on small, medium or large compute types. No instances required!