[Tooling] Automate Release Publishing #21239
Conversation
|
|
 |
App Name |  WordPress |
| Flavor | Jalapeno | |
| Build Type | Debug | |
| Version | pr21239-b0e2cf1 | |
| Commit | b0e2cf1 | |
| Direct Download | wordpress-prototype-build-pr21239-b0e2cf1.apk |
|
 |
App Name |  Jetpack |
| Flavor | Jalapeno | |
| Build Type | Debug | |
| Version | pr21239-b0e2cf1 | |
| Commit | b0e2cf1 | |
| Direct Download | jetpack-prototype-build-pr21239-b0e2cf1.apk |
| # RELEASE_VERSION is passed as an environment variable passed to Buildkite by ReleasesV2. | ||
| if [[ -z "${RELEASE_VERSION}" ]]; then |
There was a problem hiding this comment.
I've adopted the same approach in Simplenote Android. But I plan to follow it up with a dedicated PR to remove the env read here and make the pipeline pass it when they call the script.
I'm not arguing for it to happen here at this time, but keen to hear what you think of the approach: https://github.com/Automattic/simplenote-android/pull/1695/files#r1766347252
There was a problem hiding this comment.
It would also make the implementation consistent with the recent changes accessing RELEASE_VERSION in the pipeline command that we made in some iOS projects.
I think this is a good idea. It's an area where we lack some standardization.
Besides, having these scripts relying less on environment variables and having those explicit in the pipelines make things clearer and easier to follow.
This PR builds on top of #21229 and automates the release publishing, which means to:
This PR will be followed by updates to the Releases V2 tool.
This is the Android counterpart of wordpress-mobile/WordPress-iOS#23592