Cloud Build

Name: Cloud Build
Brand: Google
Rating: 4.4 (70 reviews)

Cloud Build is a managed continuous integration (CI) service that executes declarative build pipelines on Google Cloud infrastructure to build and test code, produce artifacts such as container images, push artifacts to Artifact Registry, and deploy to targets like Cloud Run or GKE.

Est 1998|Valuation $4081.3B|Raised $26.1M

LinkedIn 41.9M|Website|Web traffic 3.3M|FTEs 198,933|HQ Mountain View, California, US

MarketsCloud-Native Application Protection Platform (CNAPP)Cloud Infrastructure Providers (IaaS/PaaS)Source Code Management (SCM)Continuous Integration & Continuous Delivery (CI/CD)Application Hosting Platforms Cloud Infrastructure Providers (IaaS/PaaS)

01Competitive Landscape

Competitive Landscape

| Aspect | Cloud Build | GitHub Actions | AWS CodeBuild | |--------|-------------|----------------|---------------| | Starting Price | Published usage-based pricing by build time and machine type | Included build allowances in some GitHub plans; additional usage charged according to vendor-published metered pricing | Vendor-published usage-based pricing; free tier allowances available for select instance types | | Intended Fit | Teams deploying to GCP services such as Cloud Run, GKE, and Artifact Registry | GitHub-centric teams that want rapid setup and marketplace integrations | AWS-centric teams standardizing CI within AWS tooling | | Key Integration Strengths | Integration with GCP IAM, Artifact Registry, and GCP deploy targets | Large ecosystem of community Actions and marketplace integrations | Native integration with AWS developer tooling and services | | Typical Limitations | User-reported YAML complexity for advanced workflows; private pools often used for builds requiring private resource access and tighter network controls | Marketplace and Actions can increase variability; potential costs at scale for hosted runners | Metered compute time model with cost-management considerations; AWS-centric workflows may be less convenient for GCP deployments |

Narrative analysis

- Feature comparison (where Cloud Build is commonly cited as a fit) - Integration with GCP services and managed execution on Google infrastructure make Cloud Build a practical option for teams whose deployment targets are in GCP. - Private pools provide an option for builds that require access to private resources and tighter network control than fully shared runners. - Feature comparison (where Cloud Build may be less suitable) - For teams that prioritize a GitHub-native developer experience and an extensive marketplace of prebuilt community actions, GitHub Actions may be faster to adopt for GitHub-hosted repositories. - Pricing comparison - Cloud Build and AWS CodeBuild are both metered by compute/build time. GitHub Actions pricing is plan-based with included allowances and additional metered usage; buyers should model expected build-time and storage consumption against vendor-published pricing and allowances. - Adoption trends - Public review footprints indicate Cloud Build is commonly used within GCP-heavy stacks but has a smaller public review footprint than some broader DevOps platforms, suggesting a more focused adoption profile.

01Competitive Landscape

Competitive Landscape

Aspect	Cloud Build	GitHub Actions	AWS CodeBuild
Starting Price	Published usage-based pricing by build time and machine type	Included build allowances in some GitHub plans; additional usage charged according to vendor-published metered pricing	Vendor-published usage-based pricing; free tier allowances available for select instance types
Intended Fit	Teams deploying to GCP services such as Cloud Run, GKE, and Artifact Registry	GitHub-centric teams that want rapid setup and marketplace integrations	AWS-centric teams standardizing CI within AWS tooling
Key Integration Strengths	Integration with GCP IAM, Artifact Registry, and GCP deploy targets	Large ecosystem of community Actions and marketplace integrations	Native integration with AWS developer tooling and services
Typical Limitations	User-reported YAML complexity for advanced workflows; private pools often used for builds requiring private resource access and tighter network controls	Marketplace and Actions can increase variability; potential costs at scale for hosted runners	Metered compute time model with cost-management considerations; AWS-centric workflows may be less convenient for GCP deployments

Narrative analysis

Feature comparison (where Cloud Build is commonly cited as a fit)
- Integration with GCP services and managed execution on Google infrastructure make Cloud Build a practical option for teams whose deployment targets are in GCP.
- Private pools provide an option for builds that require access to private resources and tighter network control than fully shared runners.
Feature comparison (where Cloud Build may be less suitable)
- For teams that prioritize a GitHub-native developer experience and an extensive marketplace of prebuilt community actions, GitHub Actions may be faster to adopt for GitHub-hosted repositories.
Pricing comparison
- Cloud Build and AWS CodeBuild are both metered by compute/build time. GitHub Actions pricing is plan-based with included allowances and additional metered usage; buyers should model expected build-time and storage consumption against vendor-published pricing and allowances.
Adoption trends
- Public review footprints indicate Cloud Build is commonly used within GCP-heavy stacks but has a smaller public review footprint than some broader DevOps platforms, suggesting a more focused adoption profile.