CI/CD pipeline
An overview for CI/CD pipeline, meaning developer keeps building code after passing the test that code/features will be in Ops pipeline which is released and gets deployed, Ops will manage/ monitor application and then loop back to developers to give feedback (or collect some feedback from the client) as a plan — such as what to be improved or what is the next feature to be built.
Continuous Integration (CI)
It’s the process that developers integrate code in high frequency into a shared repository. Including developing and compiling, performing unit tests, integrating with databases, performing preproduction deployment, performing function tests, generating reports and analyzing, and code labeling. The integration process is implemented by automation tools that execute build and testing. So it can detect bugs in the stage and whenever new commits are integrated into the main branch.
Continuous Delivery (CD)
This process means test cases are passed, including compile and build. For production deployment will be deployed to Staging environment and this process will be manual any time by clicking a button.
Continuous Deployment (CD)
This process automatically deploys in to production. Prior to releasing into production, there is no final step of manual approval, which is difference from Continuous Delivery (CD).
