fix(ci): writable HOME in Production auto-deploy — unblock fleet-wide deploys (#2193) #2196
Reference in New Issue
Block a user
Delete Branch "sre/fix-auto-deploy-writable-home-2193"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fix #2193 — Production auto-deploy fails fleet-wide on unwritable HOME
The
Production auto-deployjob's git/docker credential saves fail with:because the publish runner's default
$HOME(/home/hongming) isn't writable. This halts the production rollout on every core main commit — blocking all merged changes from deploying.build-and-pushalready dodges this for buildx (DOCKER_CONFIG="$RUNNER_TEMP/docker-config"); the auto-deploy job was missing the equivalent. This adds a first step that pointsHOME+DOCKER_CONFIGat the writable$RUNNER_TEMP, mirroring that proven pattern. Narrow, env-only; deploy logic untouched.Closes #2193. Unblocks cp#511/core#2182 (google-adk SSOT) + all other stuck deploys.
qa: narrow env-only fix mirroring build-and-push's writable-config pattern; YAML-validated; deploy already broken so can only help. P1 unblock.
/qa-recheck /security-recheck
security: env-only (HOME/DOCKER_CONFIG -> RUNNER_TEMP); no secrets, no new perms, removes a host-path dependency. Approving.
/qa-recheck /security-recheck