Continuous Integration and Continuous Delivery (CICD)
Explore how continuous integration centralizes code merging and automates building and testing upon each commit. Understand continuous delivery’s role in automating deployments to test and production environments with Azure Pipelines. This lesson helps you grasp CI/CD principles to deliver software efficiently and reduce deployment risks.
We'll cover the following...
Continuous integration (CI)
Developers typically write code under source control on their own computers. They then may create a branch off of a “main” repo or work in their own fork of the repo. Developers work in a distributed fashion. CI changes that. CI brings together all of that code in one place by merging code into what’s sometimes called a mainline. This code is typically merged together multiple times per day. CI will then typically run the build process automatically.
In a CI workflow, every time a developer commits code to a repository, the build and tests run. CI automates the build trigger from a manual step to invoking the build upon each code commit. This automation then forces the code to run through the build and testing process more often, hopefully leading to a more reliable end product.
CI keeps code deployable at any time. It typically means testing and packaging up the code to ...