The past week , I read about the practice of CI/CD (Continuous Integration , Continuous Delivery) in a developing project . For newer developers , the biggest fear is doing a pull request and recognizing the countless of red underlines in our code , while it’s already a mess to develop a single branch without causing breaking changes , we can’t imagine the stress having to pull requests from multiple branches .
Continuous Integration (CI)
A solution to this problem is a to practice CI . As the goal is to have multiple developers working simultaneously on different features . It is very likely to cause changes that breaks the application . Therefore , a successful CI involves creating well-designed unit and integration tests across all modules , so that code changes can be regularly tested , built and merged to a shared repository without breaking the application in the CD stage .
Continuous Delivery (CD)
A CD picks up where the CI ends , CD automates the release of that validated code to a repository. In order to have a successful CD process , it’s essential that CI is already built into your development pipeline . The goal of CD is to have a codebase that is ready to be delivered from a SandBox environment within minutes of creation to a production environment.