mcpField
G
gpc-build-lifecycle

gpc-build-lifecycle

github.com/androidpoetCloud & DevOps442 installsUpdated 17w ago
Repository

About gpc-build-lifecycle

A skill for Android build lifecycle tasks using the gpc CLI, aimed at developers or agents uploading build artifacts and waiting for processing. It covers AABs, legacy APKs, and deobfuscation files, with guidance for CI pipelines.

Key features

  1. 01Upload and list AAB bundles
  2. 02Find bundles by version code
  3. 03Wait for bundle processing
  4. 04Upload and list legacy APKs
  5. 05Upload ProGuard mappings and native symbols
  6. 06CI build pipeline guidance

Use cases

  1. 01Upload AABs and wait for processing in CI
  2. 02Verify uploaded build artifacts
  3. 03Submit mapping and symbol files for crash reports

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/androidpoet/playconsole-cli-skills --skill gpc-build-lifecycle

After installing, type/gpc-build-lifecyclein Claude Code to confirm it loaded.

Details

From the project README

Build Lifecycle

Use this skill when uploading builds, waiting for processing, managing APKs/bundles, or uploading deobfuscation files.

Bundles (AAB)

Upload bundle
gpc bundles upload --file app.aab --track internal --package com.example.app
List uploaded bundles
gpc bundles list --package com.example.app
Find bundle by version code
gpc bundles find --version-code 42 --package com.example.app
Wait for processing
gpc bundles wait --version-code 42 --package com.example.app
gpc bundles wait --version-code 42 --timeout 600 --interval 30 --package com.example.app

APKs (legacy)

Upload APK
gpc apks upload --file app.apk --package com.example.app
List APKs
gpc apks list --package com.example.app

Deobfuscation files

Upload ProGuard mapping
gpc deobfuscation upload --version-code 42 --file mapping.txt --type proguard --package com.example.app
Upload native debug symbols
gpc deobfuscation upload --version-code 42 --file symbols.zip --type native-code --package com.example.app

CI/CD build pipeline

Typical CI flow:

# 1. Upload bundle
gpc bundles upload --file app.aab --track internal --commit --package com.example.app

# 2. Wait for processing
gpc bundles wait --version-code $VERSION_CODE --timeout 600 --package com.example.app

# 3. Upload ProGuard mapping for crash symbolication
gpc deobfuscation upload --version-code $VERSION_CODE --file mapping.txt --type proguard --package com.example.app

# 4. Promote to beta
gpc tracks promote --from internal --to beta --package com.example.app

Agent behavior

  • Always use AAB format over APK (APK upload is deprecated).
  • Upload deobfuscation files immediately after build upload.
  • Use gpc bundles wait in CI to block until processing completes.
  • Show bundle list after upload to confirm success.

Notes

  • AAB is required for new apps; APK support is for legacy apps.
  • ProGuard mappings enable readable crash stacks in Android Vitals.
  • Native debug symbols enable symbolicated native crash reports.
  • See gpc-release-flow skill for track promotion after upload.

Comments

Markdown supported