How we migrated the CI / CD of our Android app to GitHub Actions
In any software development process, the CI/CD is a crucial piece that helps teams catch the problems early, improve the code quality, automate the release process, among other benefits.
At Innovorder, we used to work with a legacy CI/CD based on Google Cloud Build. It was hard to maintain mainly because no-one in the team really knew how it worked and because of a lack of good documentation, so we ended up deciding to build a new and more reliable CI/CD.
In this session, I’ll share the story of how we migrated to GitHub
Actions. Outline challenges we faced and how we solved them. And finally show how we went even further, by improving on the previously existant CI in different ways, in terms of features, performance and even costs.
I hope to show how easy it is to build a CI for an Android project without the need of maintaining complex Docker images nor any kind of infrastructure.
Titouan is a Senior Android Engineer at Innovorder, working remotly from Lyon.
He is also passionate about theatre and languages, loves riding his bike and walking in the nature.
Lately I’ve been exploring a variety of subjects such as CI/CD, KMPP, Jetpack Compose and Compose for Desktop, Ktor, and responsible use of resources.
