Skip to content

bot: build the deploy image on the runner - #46

Merged
Na5co merged 1 commit into
mainfrom
claude/deploy-fix
Sep 23, 2026
Merged

Na5co merged 1 commit into
mainfrom
claude/deploy-fix

Conversation

@Na5co

@Na5co Na5co commented Sep 23, 2026

Copy link
Copy Markdown
Owner

The deploy workflow's first three runs failed at the build step: The user is forbidden from accessing the bucket [summer-ranger-205420_cloudbuild]. Granting serviceusage.serviceUsageConsumer, storage.admin and waiting for propagation did not fix it — Cloud Build's staging bucket needs a quota project threaded through the external-account credential, which is more moving parts than this build is worth.

Cloud Build was only there because a Mac builds arm64 and Cloud Run runs amd64. A GitHub runner is already amd64, so the workflow now builds with docker build and pushes straight to Artifact Registry. Fewer services in the path, no staging bucket, and the layer cache is local to the runner.

bot/cloudbuild.yaml stays for deploying by hand from a Mac, and says so.

🤖 Generated with Claude Code

Cloud Build's staging bucket refuses the federated credential — the quota
project is not threaded through an external account — and the workaround is
more moving parts than the build is worth. The runner is amd64 already, which
is the only reason Cloud Build was there: a Mac cross-compiles, a runner does
not.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Na5co
Na5co merged commit 1bdb721 into main Sep 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant