Skip to content

[codex] Enforce GCP release lab artifacts#108

Merged
adamcohenhillel merged 1 commit into
mainfrom
codex/repair-gcp-lab-release
Jul 2, 2026
Merged

[codex] Enforce GCP release lab artifacts#108
adamcohenhillel merged 1 commit into
mainfrom
codex/repair-gcp-lab-release

Conversation

@adamcohenhillel

Copy link
Copy Markdown
Contributor

Summary

This PR corrects the release/lab path so OpenPhone release publishing is explicitly GCP-backed instead of silently dispatching the Android compile to an ambiguous self-hosted build runner.

It:

  • replaces the release build job with a GitHub-hosted controller that authenticates to GCP via Workload Identity Federation;
  • adds scripts/lab/gcp/run-release.sh to create a disposable GCP VM, use warm cache state, build target-files/OTA tooling, run the emulator gate, copy artifacts back, and clean up;
  • adds scripts/stage-release-ota.sh to stage an OTA from target-files using Android releasetools instead of relying on the Lineage bacon wrapper as the artifact contract;
  • makes non-dry release publishing require the GCP emulator gate;
  • adds GCP lab workflow summaries with project, zone, VM, ref, cache mode, cleanup, and disabled VM identity details;
  • updates public docs/comments so AWS/EC2 and openphone-build are not described as the official OpenPhone CI/CD path.

Why

The previous release workflow looked GCP-related, but the real Android compile still used runs-on: [self-hosted, openphone-build], which resolved to non-GCP infrastructure. That defeated the goal: trusted PRs and releases need evidence from a real GCP build/emulator path, not a shallow smoke or hidden runner.

Validation

  • bash -n scripts/stage-release-ota.sh scripts/lab/gcp/run-release.sh scripts/lab/gcp/run-smoke.sh scripts/check-assistant-java.sh scripts/bootstrap-android-build-host.sh
  • Ruby YAML parse for .github/workflows/release.yml and .github/workflows/gcp-lab.yml
  • git diff --check
  • ./scripts/check.sh
  • ./scripts/check-release-notes.sh v0.0.2 docs/releases/0.0.2.md
  • Confirmed gh release view v0.0.2 still reports release not found

Remaining Before Merge

  • Run the GCP release lab path from this branch and inspect artifacts/logs.
  • Confirm the run shows GCP project/zone/VM/source/cache/emulator/artifact validation evidence.
  • Publish v0.0.2 only after that GCP build/emulator/release path passes.

@vercel

vercel Bot commented Jul 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openphone-docs Ready Ready Preview, Comment Jul 2, 2026 11:01am

Request Review

@adamcohenhillel

Copy link
Copy Markdown
Contributor Author

Validation update before merge:

Next after merge: dispatch the non-dry v0.0.2 release from main, which should build/stage/publish the real release assets through the GCP release lab.

@adamcohenhillel
adamcohenhillel marked this pull request as ready for review July 2, 2026 11:42
@adamcohenhillel
adamcohenhillel merged commit 105622e into main Jul 2, 2026
6 checks passed
@adamcohenhillel
adamcohenhillel deleted the codex/repair-gcp-lab-release branch July 2, 2026 11:42
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