The tutorial shows how to build your Android CI/CD development pipeline using Bitrise. This is part of a series for building Android Continuous Integration and Continuous Delivery (CI/CD) with Bitrise.
Android Continuous Integration (CI) makes development life cycles easier. Every time we push new code, we run a set of build tasks to check nothing was broken by our code changes. For example, when we push code we can run: Android Lint check, Unit tests, UI tests, build APK/App Bundle.
With Bitrise we can configure our Android CI process to do below build tasks.
- Android Lint (code style checks) generates an HTML report.
- Unit Tests (Jacoco and Code test coverage report) generates test results report in a zip.
- UI Integration Tests (Espresso).
- Android Build generates Free/Pro application (APK and App Bundle).
- Bitrise feature “Schedule” set an App build to run automatically daily.
- Bitrise feature “Deploy” get build status notifications email, slack, etc.
Bitrise setup: (follow instructions: https://blog.bitrise.io/from-zero-to-testing-an-android-app-on-bitrise-part-2-of-2)
- Create an Android Project (Gradle).
- Push your project to GitHub.
3. Create an account on Bitrise (Free).
4. Login to Bitrise and click button “Add New App” -> select “ Add New App on web UI”
5. Follow the Bitrise instructions:
- Link your Android Github repository to Bitrise.
Start a building Android apps :)
More posts I wrote about Bitrise:
Thanks for reading! Let me know if you have any questions or feedback
Bitrise zero to CI: good tutorial to get started with Bitrise CI for Android
From zero to testing an Android app on Bitrise (Part 2 of 2)
You have an Android app, but don’t know how to add it to Bitrise and how to create a UI and a Unit test for it? Read…
New Bitrise logic steps:
Redesigned Android scanner, steps, and workflows to make it simpler and better
Quite a few things were changed for the more convenient for our Android users. Check out how we made the Android setup…
Android Continuous Integration and Delivery — Next level Android development
** Originally published on The Tech Guru ***
What is CI/CD process
Local demo app:
Local code: AS 3.5 /../dev/HelloBitriseProject
I’ve been an Android Software Continuous Integration (CI) process fan for some years and I have noticed the following. Some people believe Software CI/CD is:
- Not important.
- Hard topic.
- Confused about how to start.
To get started with Android CI: I would recommend learning about Gradle and learning about building Android Apks/ App Bundles with small demo projects.
Maybe Google should take responsibility for the CI process, and guide developers on how to set up CI for Android. Hopefully one day Google releases a Mobile CI tool, Apple bought the CI company BuddyBuild.
Bitrise makes Android developers lifes easier, we don’t have to maintain a build machine, Docker builds environments, Dockerfile, aws, etc. The goal of CI is to make sure the code changes we push into the master branch are not going to break our release/development pipeline.
My favorite Bitrise feature is that when it builds sends build status notifications (email/slack with the Android app to install).
Some engineers are interested in Software CI/CD process :)