Setting up a CI/CD pipeline for Flutter using Codemagic
While most software development teams and companies have predominantly adopted the implementation of the Agile methodology in their approach to software development, there may be a few that may still be stuck in the past with the waterfall approach, the proverbial equivalent of living in a deserted island, unless of course they are trying to walk on water.
The need, however, for automated processes in the Agile approach could have led to the introduction of the DevOps approach to software development. One such part of the automated processes that come with DevOps is the CI/CD (Continuous Integration/ Continuous Delivery — Deployment) process. In a nutshell, CI improves on the stability of the product with each development cycle as each time code is pushed, automatic builds are triggered and integration tests are run to ensure that the new units being added do not “break” the previously successfully built application. Builds fail if tests fail, among other reasons, thus ensuring the stability of the app. Continuous Delivery is responsible for the preparation of the app for release while Continuous Deployment is responsible for automatic deployment to production.
There already exists a good number of tools for setting up CI/CD pipelines for many programming languages. This article discusses setting up a CI/CD Pipeline for a Flutter application using CodeMagic. An attempt to making sure that everyone always knows what the programmer is always doing.