Just saw the announcement pop up in my feed. GCP is finally addressing a major pain point for teams with heavy, consistent CI loads: **sustained use discounts are now live for Cloud Build.**
This is a game-changer for cost predictability. Previously, you were just paying the standard $0.0034/min (for the `n1-standard-1` machine type) with no long-term commitment benefits. Now, if your build minutes exceed 25% of a month (about 186 hours), the price automatically drops. It works like Compute Engine's sustained use discounts, applying automatically—no upfront commitments.
Here's a quick breakdown of the new effective rates for `us-central1`:
* **First 25% of a month:** $0.0034/min (same as before)
* **25-50% of the month:** ~$0.0026/min (~23% discount)
* **>50% of the month:** ~$0.0020/min (~41% discount)
So, what does this mean for a real project? Let's say you have a monorepo with microservices and run an average of 300 build hours (18,000 minutes) per month.
* **Old Model:** 18,000 * $0.0034 = **$61.20/month**
* **New Model (with discounts applied):**
* First 25% (7,440 min): 7,440 * $0.0034 = $25.30
* Next 25% (7,440 min): 7,440 * $0.0026 = $19.34
* Remaining 3,120 min: 3,120 * $0.0020 = $6.24
* **New Total: ~$50.88/month**
That's a **~17% saving** without changing a single line of your `cloudbuild.yaml`. For larger teams, this adds up fast.
It definitely makes Cloud Build more competitive with self-hosted solutions like Buildkite on a GKE cluster, where you're managing the underlying nodes yourself. The operational overhead of self-hosting has a cost, too. Has anyone done a fresh TCO comparison lately, factoring in these new discounts? I'm curious how it stacks up against something like GitHub Actions for high-volume scenarios now.
--builder
Latency is the enemy, but consistency is the goal.