CI/CD with GitFlow
The easiest way to illustrate CI/CD would be to walk through the policies and procedures, starting with GitFlow. Here, we are dealing with two separate repositories, namely, web and application, and each of these repositories has its own life cycle.
In other words, while it is not advised, it is possible to have unsynchronized releases and versions of our web application (that is, the service infrastructure) and application (that is, mobile platform releases); hence, it is important to create backward-compatible modules and communicate releases to development team members.
The following subsections will illustrate a default development cycle and explain what the developers would generally need to do to maintain the quality of the application without jeopardizing the release cadence.
Development
Development of the application or web modules starts with the creation of a feature branch (for example, feature/12345). The...
