Need advice about which tool to choose?Ask the StackShare community!
AWS CodePipeline vs Google Cloud Build: What are the differences?
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; Google Cloud Build: Continuously build, test, and deploy. Cloud Build lets you build software quickly across all languages. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase.
AWS CodePipeline and Google Cloud Build belong to "Continuous Deployment" category of the tech stack.
Some of the features offered by AWS CodePipeline are:
- Workflow Modeling
- AWS Integrations
- Pre-Built Plugins
On the other hand, Google Cloud Build provides the following key features:
- Commit to deploy in minutes
- Choose what to build
- Extremely fast builds
Volta Industries, ChromaDex, and PouchNATION are some of the popular companies that use AWS CodePipeline, whereas Google Cloud Build is used by Policygenius, 8villages, and Autingo. AWS CodePipeline has a broader approval, being mentioned in 29 company stacks & 15 developers stacks; compared to Google Cloud Build, which is listed in 10 company stacks and 6 developer stacks.
Pros of AWS CodePipeline
- Simple to set up13
- Managed service8
- GitHub integration4
- Parallel Execution3
- Automatic deployment2
- Manual Steps Available0
Pros of Google Cloud Build
- GCP easy integration1
- Container based1
Sign up to add or upvote prosMake informed product decisions
Cons of AWS CodePipeline
- No project boards2
- No integration with "Power" 365 tools1
Cons of Google Cloud Build
- Vendor lock-in2