Trigger release build instead of running it in finalize_release
#1710
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
Two reasons: 1. In it's current status if fails because of `tumblr-metal` constraints. See https://buildkite.com/automattic/simplenote-android/builds/433#0192c195-15a6-49dd-be04-e14b04eea312 2. There is a difference from simply running the lane that builds the release build and running the full CI pipeline. The latter is what we need.
Generated by 🚫 Danger |
|
📲 You can test the changes from this Pull Request in Simplenote Android by scanning the QR code below to install the corresponding build.
|
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.
Two reasons:
tumblr-metalconstraints. See https://buildkite.com/automattic/simplenote-android/builds/433#0192c195-15a6-49dd-be04-e14b04eea312Will merge without waiting for CI because none of the code changed here runs in the standard CI. We'll validate it once in the release branch by running a new release finalization attempt.