Automated Android CI/CD Pipeline: GitHub Actions, Fastlane & Play Console Deployment

Why Manual Releases Waste Engineering Hours

Manually compiling APKs, generating release notes, and uploading bundles to Google Play Console is time-consuming and prone to human error. A modern Continuous Integration and Continuous Deployment (CI/CD) pipeline automates testing, signing, and track distribution on every Git merge.

GitHub Actions Workflow (.github/workflows/deploy.yml)

name: Build & Deploy to Play Console

on:
  push:
    branches: [ main ]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Set up JDK 17
        uses: actions/setup-java@v3
        with:
          java-version: "17"
          distribution: "temurin"

      - name: Build Release Bundle
        run: ./gradlew bundleRelease

      - name: Deploy to Google Play Internal Track
        uses: r0adkll/upload-google-play@v1
        with:
          serviceAccountJsonPlainText: ${{ secrets.PLAY_CONSOLE_JSON_KEY }}
          packageName: com.jmdworld.app
          releaseFiles: app/build/outputs/bundle/release/app-release.aab
          track: internal

Automating your build pipeline ensures that every commit is vetted and deployed reliably.