Add automation to run most of the release flow in CI #22192
Merged
Conversation
This file contains 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
mokagio
force-pushed
the
mokagio/release-automation-in-ci
branch
from
2d316a1
to
30d61c3
Compare
mokagio
changed the title
This was referenced Dec 8, 2023
|
| App Name |  WordPress Alpha |
|
| Configuration | Release-Alpha | |
| Build Number | pr22192-e8deffc | |
| Version | 23.9 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | e8deffc | |
| App Center Build | WPiOS - One-Offs #8130 |
|
| App Name |  Jetpack Alpha |
|
| Configuration | Release-Alpha | |
| Build Number | pr22192-e8deffc | |
| Version | 23.9 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | e8deffc | |
| App Center Build | jetpack-installable-builds #7150 |
mokagio
commented
Dec 12, 2023
|
I am hoping to review this tomorrow once #22214 is merged and this PR is updated 🤞 |
mokagio
force-pushed
the
mokagio/release-automation-in-ci
branch
from
6c94f4d
to
29a7d19
Compare
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
force-pushed
the
mokagio/release-automation-in-ci
branch
from
29a7d19
to
e8deffc
Compare
|
I admin merged this PR to test the process "in real life" as part of the 24.0 release schedule. I feel confident in doing so without code review because none of the changes are on the app codebase. I issues arise in this PR, I can address them post-facto directly in the release branch. |
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.
Builds on top of #22191 and ports the release automation in CI work that @oguzkocer did for Jetpack and WordPress Android to this project, with some minor tweaks.
I tested this "thoroughly" by simulating a release via #22194.
Regression Notes
Potential unintended areas of impact – Some of the release automation might have broken. As the release manager, I'll deal with if I run into it.
What I did to test those areas of impact (or what existing automated tests I relied on) – Run it on test branches.
What automated tests I added (or what prevented me from doing so) – N.A.
PR submission checklist:
RELEASE-NOTES.txtif necessary. N.A.UI changes testing checklist: Not a UI PR.