Streamlining Android CI/CD with GitHub Actions and Firebase Distribution

How to Set Up Android CI/CD with GitHub Actions — Firebase Distribution & Play Store

Aleksandr Ilinskiy’s guide on setting up Android CI/CD with GitHub Actions provides a straightforward approach to building signed APKs/AABs and deploying to Firebase Distribution. The process involves creating a signing keystore, adding GitHub secrets, and configuring the workflow for Firebase Distribution and Play Store deployment.

Why This Matters

Setting up a reliable CI/CD pipeline is crucial for Android app development, as it automates the build, test, and deployment process, reducing manual errors and increasing efficiency. However, the ideal model of a seamless CI/CD pipeline often clashes with technical realities, such as permission issues, keystore management, and Gradle caching. By understanding these challenges and implementing the right strategies, developers can create a robust CI/CD pipeline that streamlines their workflow and improves overall productivity.

Key Insights

• GitHub Actions provides a convenient way to automate Android app deployment, with features like concurrency groups and tag-based triggers (GitHub, 2022)
• Firebase Distribution is an effective tool for internal testing, allowing testers to receive notifications with each new build without requiring Play Store review (Firebase, 2022)
• Gradle caching can significantly reduce build times, with the first build downloading all dependencies and subsequent builds leveraging the cache (Gradle, 2022)

Working Examples

Make gradlew executable

git update-index --chmod=+x gradlew

Configure build.gradle for CI signing

android { signingConfigs { create("release") { storeFile = file("release.jks") storePassword = System.getenv("KEYSTORE_PASSWORD") keyAlias = System.getenv("KEY_ALIAS") keyPassword = System.getenv("KEY_PASSWORD") } } }

Practical Applications

• Company: Google, Behavior: Uses GitHub Actions for automating Android app deployment, Pitfall: Failing to configure concurrency groups can lead to wasted CI minutes
• Company: Facebook, Behavior: Utilizes Firebase Distribution for internal testing, Pitfall: Not properly managing keystore secrets can result in build failures

References:

• https://dev.to/aleksandr_ilinskiy/how-to-set-up-android-cicd-with-github-actions-firebase-distribution-play-store-30nk