← All insightsCI/CD

Integrating Google Cloud into your CI/CD pipeline

Nir Geier, CodeWizard · 5 January 2026 · 3 min read · Intermediate

Getting Google Cloud into your pipeline is where it starts paying off - automated, repeatable and reviewed. Here is a working integration and the habits that keep it reliable.

A working pipeline snippet

Auth from GitHub Actions via Workload Identity Federation.

yaml
- uses: google-github-actions/auth@v2
  with:
    workload_identity_provider: projects/123/locations/global/workloadIdentityPools/gh/providers/gh
    service_account: ci@acme.iam.gserviceaccount.com

Do this

  • Use Workload Identity Federation - no exported SA keys
  • Grant least-privilege predefined roles per service account
  • Enforce uniform bucket-level access and org policies

Avoid this

  • Service-account key files instead of Workload Identity Federation
  • Primitive roles (Owner/Editor) instead of predefined/custom roles
  • Public buckets from legacy ACLs

Want senior help putting Google Cloud to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult