Part 4 of the DevOps Masterclass (CI/CD)

1. DevOps Masterclass - CI/CD
Overview
Part 4 Summary: Continuous
Integration & Delivery

2. Introduction to CI/CD
• • Part 4 of DevOps Masterclass
• • Focus on Continuous Integration (CI) &
Continuous Delivery (CD)
• • Tools: GitHub Actions, Azure DevOps
• • Emphasis on iterative, incremental delivery

3. The DevOps Cycle
• • Plan → Develop → Deliver → Operate →
Feedback
• • CI/CD enables faster and smaller releases
• • Each cycle builds measurable value
• • Continuous feedback drives improvement

4. Continuous Integration (CI)
• • Merge code frequently, ideally daily
• • Detect integration issues early
• • Automate build and test processes
• • Output: Validated artifact (e.g., Docker
image, zip)

5. CI Pipeline Process
• • Trigger: Commit or Pull Request
• • Steps:
• - Setup agent
• - Install dependencies
• - Build code
• - Run automated tests
• - Generate artifact
• - Push to registry

6. CI Runners & Environments
• • Jobs run on agents or runners
• • GitHub-hosted, Azure-hosted, or self-hosted
• • Environment consistency is key
• • Avoid manual processes for testing

7. Security in CI
• • Shift-left approach: detect issues early
• • Use tools like CodeQL, secret scanning,
Dependabot
• • Public repos: free features
• • Private repos: enterprise features required

8. Continuous Delivery (CD)
• • CD prepares production-ready code
• • Runs through multiple environments: Dev,
QA, Staging
• • Builds confidence via automated testing
• • Manual gates or approvals before
production