Building RESTful Web Services with .NET Core

CI versus CD

We have already discussed these two methods in previous sections. In this section, we will briefly discuss the difference between CI and CD.

CI is a practice where by all team members (developers) integrate their code. This happens on every check-in, whenever a developer pushes changes, or as the code is configured, CI triggers. The most important advantage of this is that it saves time during your development cycle as it identifies conflicts, if there are any. This starts with the initial steps to set up automotive tests. As soon as someone pushes changes to the repository, it triggers the build and tests.

Continuous deployment solves the deployment problems of the code while deploying to the production environment.