Publish Android App with YAML

Learn more about:

YAML parameters for Publish Android App

List with common parameters for all Buddy actions

NameTypeDescription
action
Required		StringThe name of the action.
type
Required		StringThe type of the action. Should be set to ANDROID_PLAY.
application_id
Required		StringThe ID of the Android Application.
track
Required		StringThe track type to read or modify. Can be one of production, alpha, beta, rollout, internal or custom track as configured in Google Play Console.
key_path
Required		StringThe path to the private key in JSON format with permissions to Google Play Developer Console.
apk_files
Required		APKs[]The list of sets of paths to the APKs.
user_fractionFloatPortion of the users who should get the staged rollout version of the APK (range 0.0 - 1.0). Required if track is set to rollout.
mapping_pathStringThe path to the deobfuscated file of the specified APK.
changes_pathStringThe path to the changelog file.
supersede_versionsBooleanCheck and disable superseded versions in other tracks (if any).

YAML example for Publish Android App

actions:
- action: "Publish Android App"
  type: "ANDROID_PLAY"
  trigger_time: "ON_EVERY_EXECUTION"
  application_id: "com.mycompany.mylovelyapp"
  trigger_condition: "ALWAYS"
  track: "rollout"
  user_fraction: 0.05
  key_path: "my-release-key.jks"
  mapping_path: ""
  changes_path: "changes.xml"
  supersede_versions: true
  apk_files:
  - apk_path: "my-app-release9.apk"
  - main_expansion_path: "ss"
  - patch_expansion_path: ""
Questions?

Not sure how to configure a pipeline for your process? Reach out on the live-chat, contact support, or ask our community on our forum.

Sign up for Buddy Digest

Best practices on CI/CD and fresh changelogs delivered weekly to your inbox.