Member-only story
CI/CD for a Flutter app with Github Actions: build, analyze and test
Welcome to this CI/CD series! 👋
In this article we will implement the “Continuous Integration” part of our CI/CD process 🧪📦👀
If you need more context please read my previous articles on the environments we are using and on our branching strategy.
A quick tour
Now might be a good time to show you the app.
So far we discussed different topics that were interesting and definitely needed, however they were general and not related to Flutter: it’s time to correct that!
A multi-package app
Implementing a complete CI/CD for a classical app is not always a piece of cake. I will however add a layer of complexity by dealing with a multi-package app… not because I like to suffer, but because this is what I had to do, it’s my real-world example 🤷
In this demo app (you can find the code in my Github repository), the structure is the following:
As you can see we only use two packages that are app and design_system. Obviously there is no real need in doing that for such a simple app, however the simple fact that we have two packages forces us to think differently for building, testing and everything: that’s what we are going to…
