-
Notifications
You must be signed in to change notification settings - Fork 99
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
Beta release workflow #113
base: main
Are you sure you want to change the base?
Conversation
echo "This will fail because we don't have the secrets configured yet" | ||
echo "$ANDROID_KEYSTORE_FILE" > keystore.jks.b64 | ||
base64 -d -i keystore.jks.b64 > app/keystore.jks | ||
echo "storeFile=keystore.jks" >> keystore.properties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The workflow from which this was based on (here) creates the keystore.properties
manually, but we can just base64 encode it whole instead if that feels cleaner. In that case we can replace KEYSTORE_KEY_ALIAS
, KEYSTORE_KEY_PASSWORD
and KEYSTORE_STORE_PASSWORD
for a single secret. I don't feel strongly about either approach
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep it separate. it will be easier to update
…fdoxyz/beta-release-workflow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are blocked by Google's key limit :\
@maestromac yeah, until we can find a way to work around this I'm making this a Draft 👍 |
What type of PR is this? (check all applicable)
Description
Adds CD to our pipeline for a more streamlined release process
Related Tickets & Documents
#81
[optional] What gif best describes this PR or how it makes you feel?