forked from bitrise-io/devcenter
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Anna Banyik updated _articles/en/deploy/android-deploy/deploying-android-apps.md
- Loading branch information
1 parent
ccd6032
commit bf55882
Showing
1 changed file
with
9 additions
and
9 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -107,7 +107,7 @@ Now let's head back to Bitrise and finish off the deploy configuration! | |
|
||
`BITRISEIO_SERVICE_ACCOUNT_JSON_KEY_URL` | ||
6. Go back to your Workflow Editor and add the **Google Play Deploy** Step to the end of your Workflow. | ||
7. In the **Service Account JSON key file path** input, paste the Environment Variable which was generated when you uploaded the service account JSON key in the **GENERIC FILE STORAGE**. Note that besides the Environment Variable, this field can also accept a remote and a file path URL as well: | ||
7. In the **Service Account JSON key file path** input, paste the Environment Variable which was generated when you uploaded the service account JSON key in the **GENERIC FILE STORAGE**. Note that besides the Environment Variable, this field can also accept a remote and a file path URL: | ||
* For remote JSON key file you can provide any download location, for example, `https://URL/TO/key.json`. | ||
* For local JSON key file you can provide a file path url, for example, `file://PATH/TO/key.json`. | ||
8. **Package name**: the package name of your Android app. | ||
|
@@ -119,25 +119,25 @@ The final configuration looks like this: | |
workflows: | ||
deploy: | ||
steps: | ||
- activate-ssh-key@3.1.1: | ||
- activate-ssh-key@4.0.5: | ||
run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}' | ||
- [email protected].11: {} | ||
- [email protected].17: {} | ||
- [email protected]: {} | ||
- [email protected]: | ||
title: Do anything with Script step | ||
- install-missing-android-tools@2.1.1: {} | ||
- android-build@0.9.4: | ||
- install-missing-android-tools@2.3.7: {} | ||
- android-build@0.10.0: | ||
inputs: | ||
- project_location: $BITRISE_SOURCE_DIR | ||
- module: "app" | ||
- sign-APK@1.2.0: {} | ||
- google-play-deploy@1.5.0: | ||
- sign-APK@1.4.1: {} | ||
- google-play-deploy@3.0.1: | ||
inputs: | ||
- package_name: io.bitrise.googleplay | ||
- service_account_json_key_path: "$BITRISEIO_SERVICE_ACCOUNT_JSON_KEY_URL" | ||
- track: alpha | ||
- deploy-to-bitrise-io@1.3.12: {} | ||
- cache-push@2.0.5: {} | ||
- deploy-to-bitrise-io@1.9.4: {} | ||
- cache-push@2.2.3: {} | ||
{% endraw %} | ||
|
||
Your workflow is ready for deploying your app automatically to [Google Play Store](https://play.google.com/store). Once the app is tested and generated, you can upload it to Google Play Store. | ||
|