Course last updated: 21/05/2024
When it comes to developing Android Apps, there's so much more than building features. We need to think about the entire development process, from checking our code functions, to making it available to users on application stores. While we can manually handle all of these tasks, this puts extra responsibility on our developers, opens up room for error and doesn't scale well as our team grows.
In this book, learn how we can use GitHub Actions to introduce Continuous Integration and Delivery into our Android projects. With its low effort and extensible API, we can create worksflows specific to the needs of our project, taking our development workflow to the next level.
π
Learn a range of fundamental concepts surrounding GitHub Actions, giving you essential knowledge for working with the framework and build your own workflows outside of the provided examples
π§ͺ
Run unit tests across your Android project with your Actions workflows. You'll learn how to run them for the whole project, along with conditionally running them for changed modules in Pull Rqeuests
π²
Learn how to run UI tests across your Android project using both Emulators and Firebase Test Lab. We'll cover how to run these for both the whole project, and conditionally for changed modules
βοΈ
You'll learn various ways to run workflows through different events that are triggered within your GitHub repository - including pull requests, manual triggers, git tags and more
π
So that we can automate releases to the Play Store, you'll learn how to build app bundles and APKs within GitHub Actions, Sign then and then Upload them to the Play Store for review + release
π
Using a combination of triggers and scripts for automated versioning, you'll learn how to uitlise scheduled workflows to build and release nightly releases through GitHub Actions
π οΈ
Learn how to integrate with external tools in our development workflow, such as communicating with Slack and Jira from directly within our Actions workflows
πββοΈ
We'll cover various optimations you can make within your actions - such as calculating changed modules in pull requests to isolate test runs to changed code
Number of team members:
Save