Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs Google Cloud Build: What are the differences?
Introduction
Azure DevOps and Google Cloud Build are two popular platforms used for managing and automating the software development lifecycle. While both platforms offer similar functionalities, there are some key differences that set them apart.
Pricing Model: Azure DevOps follows a tier-based pricing model that includes a free tier with limited features and paid plans based on the number of users. On the other hand, Google Cloud Build offers a flexible pricing model based on usage, allowing users to pay for only the resources they consume.
Integration with Cloud Services: Azure DevOps is tightly integrated with Microsoft Azure's cloud services, providing seamless integration and direct access to Azure resources for building, deploying, and managing applications. In contrast, Google Cloud Build is designed to work with Google Cloud Platform (GCP) services, offering native integration with GCP services and resources.
Build Environment: Azure DevOps provides a customizable build environment that allows users to define their own build agents and tools, enabling flexibility in building and deploying applications. Google Cloud Build, on the other hand, uses pre-defined build environments based on containers, offering a more standardized approach to building applications.
Supported Version Control Systems: Azure DevOps supports both Git and Team Foundation Version Control (TFVC), providing flexibility for developers to choose their preferred version control system. In contrast, Google Cloud Build primarily supports Git as the version control system, limiting the options for developers who prefer TFVC.
Access Control and Permissions: Azure DevOps offers robust access control and permission settings, allowing users to define fine-grained access controls for various parts of the platform. Google Cloud Build provides basic access control capabilities, but it may not offer the same level of granularity and control as Azure DevOps.
Third-Party Integration: Azure DevOps has a wide range of integrations with third-party tools and services, allowing users to seamlessly connect and integrate their development and deployment workflows. Google Cloud Build also has some integrations, but it may not have the same extensive ecosystem of integrations as Azure DevOps.
In summary, Azure DevOps and Google Cloud Build differ in their pricing model, integration with cloud services, build environment approach, supported version control systems, access control and permissions, and third-party integration capabilities.
Pros of Azure DevOps
- Complete and powerful56
- Huge extension ecosystem32
- Azure integration27
- Flexible and powerful26
- One Stop Shop For Build server, Project Mgt, CDCI26
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- Cost free for Stakeholders6
- One 4 all6
- Crap6
- Project Mgmt Features6
- Runs in the cloud5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Link Test Cases to Stories2
- Jenkins Integration2
- GCP Integration1
Pros of Google Cloud Build
- GCP easy integration2
- Container based2
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents8
- Half Baked5
- Many in devops disregard MS altogether5
- Not a requirements management tool4
- Jack of all trades, master of none4
- Capacity across cross functional teams not visibile4
- Poor Jenkins integration3
- Tedious for test plan/case creation2
- Switching accounts is impossible1
Cons of Google Cloud Build
- Vendor lock-in2