Skip to content

feat(ci): Dual-flavor parallel build — ThirdParty + Play Debug#1

Merged
criollojoel10 merged 1 commit into
mainfrom
feat/dual-flavor-build
Jun 8, 2026
Merged

feat(ci): Dual-flavor parallel build — ThirdParty + Play Debug#1
criollojoel10 merged 1 commit into
mainfrom
feat/dual-flavor-build

Conversation

@criollojoel10

Copy link
Copy Markdown
Owner

🔧 Cambios

Reescribe android-build.yml con compilación dual en paralelo:

📦 Dos flavors en paralelo (matrix strategy)

Flavor Gradle Task Capacidades
thirdParty assembleThirdPartyDebug SMS, Call Log, Fotos, nodo completo
play assemblePlayDebug Sin SMS/Call Log (política Play Store)

✨ Mejoras

  • Matrix strategy — ambos flavors compilan en runners separados (paralelo)
  • Debug builds — más rápido, sin firmar, ideal para sideload
  • SHA256 checksums — archivos .sha256 junto a cada APK
  • Release única — tag android-v{VERSION}-b{RUN} con ambos APKs + checksums
  • Release body — instrucciones de instalación por flavor
  • Jobs encadenados: check → build (×2 parallel) → release

🔄 Sin cambios

  • Upstream sync (openclaw/openclaw)
  • Detección de cambios en apps/android/
  • Cron cada 6h + workflow_dispatch

⚠️ Notas

  • Debug APKs no están firmados → hay que desinstalar antes de cambiar entre CI y releases oficiales
  • La detección de cambios compara HEAD local vs upstream/main, igual que antes

- Matrix strategy: builds thirdParty and play in parallel
- Both Debug builds (unsigned, for sideloading)
- SHA256 checksums per APK
- Single release with both APKs + checksums
- Upstream sync + change detection preserved
- Tag format: android-v{VERSION}-b{RUN}
- Release body with install instructions per flavor
@criollojoel10 criollojoel10 merged commit 99ecfb1 into main Jun 8, 2026
70 of 81 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant