CI is the automated process of retrieving application code from one or more code repositories, building the code, and running unit tests. CD is an automated process of delivering/deploying the application build artifacts to one or more environments, such as quality assurance (QA), user acceptance testing (UAT), and production. The CD process begins with the successful completion of the CI process. The following diagram shows both CI and CD processes:
Figure 1: CI/CD Process
These are some of the important aspects of the CI/CD process in the preceding diagram:
- Developers commit the code: To start with, one or more developers commits the application code, they have been working upon. This includes both, Angular app and Spring Web app developers.
- Code repository triggers CI: As the code changes are pushed into the code repository (GitLab in the preceding diagram), GitLab webhooks triggers the CI builds in CI tool such as Jenkins. The process to achieve the automated trigger...