A curated list of high-signal resources for Google Cloud Build in 2026: CI, triggers, private pools, Artifact Registry, supply chain security, and modern delivery pipelines.
Cloud Build is Google Cloud's managed build platform for running CI pipelines, building containers and packages, generating provenance, and shipping artifacts into services such as Artifact Registry, Cloud Run, GKE, App Engine, and Cloud Deploy.
In 2026, the Cloud Build ecosystem is materially different from the 2021 version of this list:
- Artifact Registry is the default artifact destination; Container Registry is deprecated and has been shut down in stages.
- Private pools, regional builds, and larger machine families are mainstream for enterprise workloads.
- Cloud Build repositories (2nd gen) and Developer Connect are the modern source integration model for GitHub, GitLab, and Bitbucket.
- SLSA provenance, security insights, and Software Delivery Shield have made Cloud Build part of Google Cloud's software supply chain security story.
- Cloud Deploy is now the recommended managed CD layer when you want promotion logic beyond "build and deploy in one file".
- Useful links
- What's new since 2021
- Quickstarts
- Tutorials
- Security & Supply Chain
- Repositories, Triggers & Source Integrations
- Private Pools & Regional Builds
- Cloud Deploy & Delivery
- AI/ML & Troubleshooting
- Migration & Deprecations
- Articles
- Cloud Builders
- Community Cloud Builders
- Cloud Build Configuration File Templates
- Tools
- Meetups
- Cloud Build product page
- Cloud Build documentation
- Cloud Build release notes
- Build configuration file schema
- Cloud Build pricing
- Cloud Build quotas and limits
- Cloud Build locations
- Cloud Build console
- CI/CD on Google Cloud
- Artifact Registry documentation
- Cloud Deploy documentation
- Cloud Build public issue tracker component
- Official builder catalog
- Community builder catalog
- Cloud Build samples
- Cloud Build notifiers
- Google Cloud buildpacks
- Stack Overflow:
google-cloud-build
2021: Private pools reached GA, making VPC-connected, enterprise-isolated builds a first-class option.2022: Regional builds and triggers went GA, which matters for data residency, latency, and private networking.2022: Software Delivery Shield launched to connect Cloud Build, Artifact Registry, Binary Authorization, and provenance into one supply chain story.2023: Cloud Build repositories (2nd gen) entered preview and then GA, modernizing repository connections beyond the original trigger model.2023: Cloud Build added SLSA v1.0 build provenance support and Google-signed OIDC identity tokens for more secure downstream integrations.2023: The free tier changed to align with thee2-standard-2default machine type and newer pricing tiers.2024: Bitbucket Cloud and Bitbucket Data Center support arrived for 2nd gen source integrations.2024: New-project behavior for the default Cloud Build service account changed; explicit user-managed service accounts are now the safer default pattern.2024: More organization policy controls landed, including custom constraints for Cloud Build resources.2025: Developer Connect-backed triggers reached GA, which is now the preferred route for several source providers.2025: Private pool machine families expanded again, includingc3andn2d, for higher-performance builds.2025: Build graph quality-of-life features improved with custom Pub/Sub topics, build dependency support, and better log field mapping.
- Build and push a Docker image
- Build Go applications
- Build Java applications
- Build Node.js applications
- Build applications with buildpacks
- Deploy to Cloud Run with Cloud Build
- Create and manage build triggers
- Store build artifacts in Artifact Registry
- Create your first Cloud Deploy pipeline
- GitOps-style continuous delivery with Cloud Build and GKE
- Access private GitHub repositories from builds
- Run builds from GitHub
- Use private pools in a private network
- Access private GKE clusters from private pools
- Configure third-party notifications
- Generate and validate build provenance
- View security insights for builds
- Manage build dependencies
- Speed up builds
- Best practices for speeding up builds
- Use manual, Pub/Sub, and webhook triggers
- Deploy to Cloud Run using Cloud Deploy
- Deploy to GKE using Cloud Deploy
- Build and deploy on GitHub with Workload Identity Federation
- Secure your builds overview
- Generate and validate SLSA build provenance
- Use Google-signed OIDC tokens
- View build security insights
- Use user-specified service accounts
- Configure private pools
- Software Delivery Shield overview
- Artifact Analysis and SBOM guidance
- Binary Authorization documentation
- SLSA verifier
- Cloud Build repositories overview
- Create and manage repositories
- Developer Connect overview
- Create and manage triggers
- Build repositories from GitHub
- Build repositories from GitHub Enterprise
- Build repositories from GitLab
- Build repositories from GitLab Enterprise
- Build repositories from Bitbucket Cloud
- Build repositories from Bitbucket Data Center
- Webhook triggers
- Pub/Sub triggers
- Manual triggers
Architecture note: Cloud Build still supports repository, webhook, Pub/Sub, and manual triggers. For broader event-driven automation across products, teams increasingly pair Cloud Build with Eventarc, Workflows, or Cloud Run rather than treating Cloud Build triggers as the only orchestration layer.
- Private pools overview
- Create and manage private pools
- Use private pools in a private network
- Access private GKE clusters with private pools
- Cloud Build locations
- Cloud Build pricing
- Choose machine types and CPU scaling options
- Cloud Deploy overview
- Cloud Deploy quickstart for Cloud Run
- Cloud Deploy quickstart for GKE
- Cloud Deploy delivery pipelines
- Skaffold documentation
- Progressive delivery on Google Cloud
Why this matters: Cloud Build remains excellent for CI and for simple "build then deploy" flows. Once you need staged promotions, approvals, rollouts, or environment-specific release controls, use Cloud Build to create artifacts and Cloud Deploy to own the CD pipeline.
- Boost your Continuous Delivery pipeline with Generative AI
- Free to be SRE: How to use generative AI for root cause analysis and remediation
- Gemini Cloud Assist plus Personalized Service Health
- Troubleshoot build failures
Cloud Build does not yet have a single "Gemini mode" that replaces build authoring. The current pattern is AI-assisted troubleshooting, release analysis, and remediation around Cloud Build logs, Cloud Deploy rollouts, and production signals.
- Transition from Container Registry to Artifact Registry
- Container Registry shutdown details
- Cloud Build service account change
- Create and manage repositories
- Cloud Source Repositories notice
- Compute Engine container startup agent deprecation
Important migrations to plan for:
- Move all
gcr.ioand*.gcr.ioflows to Artifact Registry-managed repositories, even when you keep thegcr.iohostname for compatibility. - Prefer Cloud Build repositories (2nd gen) or Developer Connect for new SCM integrations.
- Stop relying on the legacy default Cloud Build service account behavior; pin builds to a least-privilege service account explicitly.
- Do not use deprecated Compute Engine container startup agent workflows such as
create-with-containerfor new deployments.
- Cloud Build release notes
- Software Delivery Shield: secure your software supply chain
- DevSecOps and CI/CD using Google Cloud built-in services
- Boost your Continuous Delivery pipeline with Generative AI
- Free to be SRE: generative AI for root cause analysis and remediation
- Personalized Service Health with Gemini Cloud Assist
- Deploy applications to Cloud Run with Cloud Build
- Best practices for building containers
Supported builder images live in the official cloud-builders repository. Start there before creating a custom builder.
Also useful:
Community-contributed builders live in cloud-builders-community. These are source projects, not hosted public images; build and publish the ones you trust into your own Artifact Registry repository before using them in production.
- kaniko
- buildah
- terraform
- terragrunt
- packer
- pulumi
- helm
- kustomize
- skaffold
- firebase
- awscli
- az
- ansible
- shellcheck
The templates in build-config-templates/ are modernized for Artifact Registry, regional builds, Cloud Deploy, multi-arch images, and private pools.
- Build and push to Artifact Registry
- Deploy to Cloud Run
- Deploy to App Engine
- Deploy to Compute Engine
- Create a Cloud Deploy release
- Build and push a multi-arch image
- Run builds on a private pool
- Cloud Build samples Reference pipelines for Docker, Cloud Run, Functions, private pools, caching, and monorepos.
- Cloud Build notifiers Official Slack, SMTP, HTTP, BigQuery, Google Chat, and GitHub Issue notifier support.
- Google Cloud buildpacks Google-maintained buildpacks for Cloud Run, Cloud Functions, and container builds.
- google-github-actions/auth Workload Identity Federation from GitHub Actions into Google Cloud.
- Skaffold Build, tag, and render support that pairs well with Cloud Build and Cloud Deploy.
- pack Local CLI for buildpacks workflows before moving them into Cloud Build.
- SLSA verifier Verify provenance emitted by Cloud Build.
- Terraform Google provider Manage triggers, repositories, worker pools, Artifact Registry, and Cloud Deploy infrastructure as code.
- buildstatus Slack notifications from Cloud Build using Cloud Run.
- buildhub.dev Hosted Slack notifications for Cloud Build.
- cloudbuild-slack Slack notifier for Cloud Build using Cloud Functions.
- gcb-visualizer Visualize Cloud Build pipelines with Graphviz.
If you want recurring, current Cloud Build content, Google Cloud events, Cloud Next sessions, and the Google Cloud Tech channel are more reliable in 2026 than older meetup pages.
