Cloud Build stages and artifact expiration
ProductionV2 jobs use specific stages and preserve source, configuration, logs, errors, artifacts, and linked retries.
What this does
Distinguishes inspection, checkout, install, web build, output verification, Capacitor sync, native compile, signing, validation, upload, completion, and failure.
What you need
A confirmed configuration and future enabled V2 dispatch.
What LaunchLayer automates
Source Build Readiness Contract generation from the exact source identity, controlled commands, output directory, target platforms, environment-variable names, and signing metadata. Actual arbitrary-source dispatch remains disabled until the isolated runner and artifact-validation boundary is released.
What remains external
Runner capacity, source fixes, signing ownership, and timely artifact download.
Exact setup steps
V2 dispatch is not released in Phase 1; legacy Cloud Build remains unchanged.
How to verify it
Every future job must record exact commit/archive hash and configuration, and retry must create a new linked record.
Common failures
Dependency error, missing output, signing failure, missing artifact, or expiration.
Security considerations
Artifacts require authorized or signed downloads and must remain tenant-isolated.
Related articles
Real GitHub source builds; Android debug APK; Certificate Center.