Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test branch for release automation in CI #22194

Closed
wants to merge 24 commits into from

Conversation

mokagio
Copy link
Contributor

@mokagio mokagio commented Dec 8, 2023

This is to test #22192.

Update: The PR was created before the changes from #22214 , as such, it's now out of sync with #22192. Still, the overall logic is the same, as the #22214 changes were mostly tweaks. The only main difference, trivial I hope, is that these tests run without the logic that creates the integration branch for the beta e8deffc

Step 1 trigger_code_freeze_in_ci

image image

Build example: https://buildkite.com/automattic/wordpress-ios/builds/18998

Step 2 trigger_complete_code_freeze_in_ci

When no release version given:

image

With release_version:23.9

image image

Build: https://buildkite.com/automattic/wordpress-ios/builds/19019
Integration PR: #22195

image

Step 3 release notes editorialization

Use the lane to create the editorialization branch, bundle exec fastlane create_editorial_branch branch:release/23.9-test (the branch parameter is only needed in this test because of the test flow where the code freeze hasn't been merged into trunk). After adding the editorialized release notes, push, and trigger the CI build with trigger_update_app_store_strings

image

Build: https://buildkite.com/automattic/wordpress-ios/builds/19023#_
Integration PR: #22196

Step 4 trigger_new_beta_release_in_ci

Build: https://buildkite.com/automattic/wordpress-ios/builds/19052
Integration PR: N.A. – Unfortunately the localization linting fails, which prevents deploying and creating a PR

image

On the other hand, it's a good demo of how the build would fail once rolled out. It makes me think that we might want to surface those failures as build annotations.

Note: this build failed because the 23.9 code freeze hadn't been merged on trunk yet so the computed version release_version_current turned out to be 23.8, for which a release branch no longer exists. With the move to the bot opening the integration PRs for us, this should become an even rarer occurrence, given the release manager will be able to merge the integration PR themselves.

Step 5 trigger_finalize_release_in_ci

image

Build: https://buildkite.com/automattic/wordpress-ios/builds/19054
Integration PR: #22209

image

@mokagio mokagio changed the base branch from trunk to mokagio/release-automation-in-ci December 8, 2023 05:35
This test build failed in a way that made me think might be due to not
enough time having passed between the branch push to GitHub and the
request to set protection,
https://buildkite.com/automattic/wordpress-ios/builds/18989
@mokagio mokagio force-pushed the release/test-release-automation branch from ab083f0 to c8997b3 Compare December 8, 2023 05:55
@wpmobilebot
Copy link
Contributor

wpmobilebot commented Dec 8, 2023

WordPress Alpha📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
App NameWordPress Alpha WordPress Alpha
ConfigurationRelease-Alpha
Build Numberpr22194-9e4281d
Version23.8
Bundle IDorg.wordpress.alpha
Commit9e4281d
App Center BuildWPiOS - One-Offs #8106
Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Dec 8, 2023

Jetpack Alpha📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
App NameJetpack Alpha Jetpack Alpha
ConfigurationRelease-Alpha
Build Numberpr22194-9e4281d
Version23.8
Bundle IDcom.jetpack.alpha
Commit9e4281d
App Center Buildjetpack-installable-builds #7126
Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

@mokagio mokagio force-pushed the release/test-release-automation branch 2 times, most recently from 756e8ed to 394e5b8 Compare December 8, 2023 06:59
@mokagio mokagio force-pushed the release/test-release-automation branch from 394e5b8 to a4e2dd3 Compare December 8, 2023 07:21
@mokagio mokagio force-pushed the release/test-release-automation branch from 6f3bd05 to 62bb18a Compare December 8, 2023 07:45
@mokagio mokagio changed the title Test branch for release automation in CI #22193 Test branch for release automation in CI Dec 12, 2023
@wpmobilebot
Copy link
Contributor

1 Error
🚫 PR requires at least one label.

Generated by 🚫 Danger

@mokagio mokagio force-pushed the mokagio/release-automation-in-ci branch 2 times, most recently from 29a7d19 to e8deffc Compare December 14, 2023 01:34
Base automatically changed from mokagio/release-automation-in-ci to trunk January 7, 2024 23:43
@mokagio mokagio closed this Jan 8, 2024
@mokagio mokagio deleted the release/test-release-automation branch January 8, 2024 00:00
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.

None yet

2 participants