CI/CD

The pipeline, in addition to being based on the DevOps Lifecycle, follows the Continuous Integration / Continuous Delivery model.

👉

The project is using Continuous Delivery (manual push in production) rather than Continuous Deployment (automatic push in production) in order to have control over what will be deployed to end users.

Gitlab CI will be used to make the pipeline, this implies that the project will be hosted on Gitlab.

Here is what a CI/CD pipeline should look like:

Taking the concepts mentioned in the DevOps Lifecycle, it is easy to understand that CI is the responsibility of Dev, while CD is the responsibility of Ops.

Depending on the problematics, some teams integrate Review/Test, Staging/Pre-production and Production environments in their CD; while others tend to reduce it by cutting either the Review or the Staging. This project being a learning project, having an application with minor bugs solved in the future within the production is not an issue. Staging will therefore be shortened, in order to greatly lighten the pipeline, since we avoid reproducing a clone environment of the production.

All that remains is to explore the final elements specific to Dev, Ops & FinOps, before viewing the complete pipeline structure.