CI/CD the journey of a dummy team

This article tries to help people in how to achieve CI/CD starting from a feature branching model (gitflow).

State of the art

Imagine we are working in a feature team that follows gitflow model, also we have sprints of 2 weeks. The team is working in a business line, is composed by 4 developers and one qa member apart from the PO and one UX person.
Let’s imagine that we want to add a log line in one part of our code and put it in production. The steps to make this happens are:

• clone the project (1s)
• create a feature branch with the name of the task (1s)
• develop your changes with tests (60s)
• test manually your changes locally (2m)
• push your code to the remote repository (1s)
• ask for a code review (5m)
• the code review is started by some colleagues (1 hour)
• the code review is passed (5m)
• put your code in one testing environment, manually?? (5m)
• ask for the qa person to verify the code (1m)
• qa tests your code (1h)
• merge your branch to master and resolve conflicts (1s)
• wait until the release is created for the sprint (1week)
• qa tests the release in a pre-prod environment (1 hour)
• deploy your changes in production (10m)