Add per-commit TestFlight builds for WordPress, Jetpack, and Reader#25674
Draft
jkmassel wants to merge 2 commits into
Draft
Add per-commit TestFlight builds for WordPress, Jetpack, and Reader#25674jkmassel wants to merge 2 commits into
jkmassel wants to merge 2 commits into
Conversation
Phase 1 of the "Faster Releases" RFC: every CI build produces a TestFlight build for all three apps, using the Buildkite build number as the build code. - `build_and_upload_app_for_testflight(app:)` builds one app and uploads it to TestFlight for internal testers only. - `.buildkite/commands/build-and-upload-testflight.sh` runs it, fanned out per app via a Buildkite matrix step. - Build code = `<VERSION_SHORT>.0.<BUILDKITE_BUILD_NUMBER>`. Intentionally not gated to trunk yet so the flow can be exercised in CI. The existing release pipeline is untouched.
Collaborator
Generated by 🚫 Danger |
Contributor
|
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 32723 | |
| Version | PR #25674 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | 21e91d4 | |
| Installation URL | 3b15ja0d6oe9g |
Contributor
|
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 32723 | |
| Version | PR #25674 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | 21e91d4 | |
| Installation URL | 2obd6deg6muto |
Contributor
🤖 Build Failure AnalysisThis build has failures. Claude has analyzed them - check the build annotations for details. |
Reader's App Store archive has been broken since #25321 (PostHelper moved to the app target without updating the Reader target), and went undetected after #25179 removed Reader from CI. WordPress and Jetpack build and upload fine. Reader is commented out of the matrix and the local wrapper; the per-app lane still supports `app: 'reader'`, so re-enabling is a one-line change once the Reader target archives again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Phase 1 of the Faster Releases RFC: make every CI build produce a TestFlight build for WordPress, Jetpack, and Reader, so that "releasing" can later become "submit a build that's already been in TestFlight for days."
This is additive — the existing code-freeze / beta / finalize release pipeline is untouched and remains the source of truth until this flow is proven.
What's here
build_and_upload_app_for_testflight(app:)(fastlane/lanes/build.rb) — builds one app for the App Store and uploads it to TestFlight for internal testers only (distribute_external: false). Build code =<VERSION_SHORT>.0.<BUILDKITE_BUILD_NUMBER>viaxcargs, the same mechanism Reader and prototype builds already use. Keeps the Sentry dSYM + Gutenberg sourcemap uploads for WP/JP..buildkite/commands/build-and-upload-testflight.sh— per-app entry point, mirrors the existingrelease-build-*.shsetup..buildkite/pipeline.yml) — fans out overwordpress/jetpack/readerin parallel.Decisions (from the RFC discussion)
VERSION_SHORTleft as-is; the versioning / pre-allocation strategy is deferred to go-live.The matrix step is intentionally not gated to trunk so we can exercise it in CI on this branch. Before merge, gate each step with
if: "build.branch == 'trunk'"(there's aTODOinpipeline.yml). Note that Reader's marketing version moves from the0.0placeholder to the sharedVERSION_SHORT.Testing instructions
<VERSION_SHORT>.0.<this build number>and that no external testers were notified.