Continuous Integration and Delivery What is CICD?
Learning objective: By the end of this lesson, learners will be able to differentiate between Continuous Integration, Continuous Delivery, and Continuous Deployment.
Intro to CICD
Who doesn’t want to save time and resources while delivering high-quality software? Continuous Integration (CI) and Continuous Delivery (CD) are practices that help you build, test, and deploy software efficiently and reliably. By adopting these practices, teams can deliver value to users faster and with greater confidence.
-
Companies typically begin with Continuous Integration (CI). CI focuses on integrating code changes into a shared repository frequently, followed by automated testing to catch issues early.
-
Continuous Delivery (CD) builds on CI by automating the deployment of tested code to staging or production environments. This includes automating infrastructure and configuration changes, ensuring deployments are consistent and repeatable.
-
For teams that want to take it a step further, there’s Continuous Deployment, which automatically deploys every change that passes tests directly to production, without manual intervention.
By the end of this module, you’ll understand these concepts and their differences, giving you a foundation for adopting modern engineering practices that enhance efficiency and quality.