Add a scheduled trunk → Play internal build#23058
Draft
oguzkocer wants to merge 2 commits into
Draft
Conversation
New build_and_upload_trunk_internal lane builds WordPress & Jetpack from trunk and uploads them to the Play Store internal track, to validate the release-from-trunk model. versionName = planned release (no -rc); versionCode via release-toolkit's ContinuousBuildCodeFormatter, written to version.properties for the build only (not committed). Adds a command script + a scheduled pipeline (manually triggerable via the PIPELINE env).
Collaborator
Generated by 🚫 Danger |
Contributor
|
|
Contributor
|
|
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
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
Adds a build that compiles WordPress & Jetpack from
trunkand uploads them to the Play Storeinternaltesting track. Part of the Faster Releases effort.build_and_upload_trunk_internallane (fastlane/lanes/build.rb): computes the version on the fly and writes it toversion.propertiesfor the build only (it will not get committed):versionName— the planned release version without the-rc-Nsuffix (current_release_version).versionCode— via release-toolkit'sContinuousBuildCodeFormatter:(major * 10 + minor) * 1_000_000 + BUILDKITE_BUILD_NUMBER. Monotonic, because Buildkite build numbers are global and only increase.It then builds WordPress & Jetpack and uploads each to the
internaltrack via the existingupload_build_to_play_store(uploaded as a draft, so no testers are notified)..buildkite/commands/build-trunk-internal.sh:install_gems+configure_apply+ the lane..buildkite/schedules/build-trunk-internal.yml: the scheduled pipeline.Testing instructions
The lane is schedule-triggered, so normal PR CI does not exercise it. To verify it manually:
wordpress-androidpipeline for this branch with envPIPELINE=schedules/build-trunk-internal.yml.internaltrack as drafts (no testers notified).versionNameand versionCode(major * 10 + minor) * 1_000_000 + <build number>.