Travis configuration with Fastlane #79
Closed
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
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.
What type of PR is this? (check all applicable)
Description
Ideally when commits are merged into
masteror when using a specific tag we could rely on Fastlane for Continuous Delivery to our Beta Track in Google Play. This release process has been a little difficult to finish so this is a WIP.Any suggestions to get this working (while safely handling credentials) are very welcome. My fork's branch has Travis Enabled see here
TODO:
google-service.jsonfile in Travis (possibly encoded in Base64 as ENV variable)[optional] What gif best describes this PR or how it makes you feel?