-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

ASP.NET 8 Best Practices
By :

In this section, we’ll learn about what continuous integration and continuous deployment mean to developers.
Continuous Integration (CI) is the process of merging all developers’ code into a mainline to trigger an automatic build process so that you can quickly identify issues with a code base using unit tests and code analysis.
When a developer checks their code into a branch, it’s reviewed by peer developers. Once accepted, it’s merged into a mainline and automatically starts a build process. This build process will be covered shortly.
Continuous Deployment (CD) is the process of consistently creating software to deploy it at any time.
Once everything has been built through the automated process, the build prepares the compiled code and creates artifacts. These artifacts are used for consistent deployments across various environments, such as development, staging, and production.
The benefits of implementing a CI/CD pipeline outweigh not having one:
In this section, we reviewed the definition of what continuous integration and continuous deployment mean when developing software in an automated fashion and the benefits of implementing a CI/CD pipeline.
In the next section, we’ll learn about certain code practices to avoid when automating software builds.