CI/CD with Azure DevOps

# CHAPTER 17

CI/CD with Azure DevOps #

1. Introduction #

2. Learning Objectives #

• Define Continuous Integration (CI) and Continuous Deployment (CD).

• Understand the role of Azure DevOps Services (Repos, Boards, Pipelines).

• Author an azure-pipelines.yml configuration file.

• Understand Pipeline Agents (Microsoft-hosted vs. Self-hosted).

• Automate the deployment of an application to Azure App Service.

3. Beginner-Friendly Explanation #

• Manual Deployment (The Old Way): An engineer designs a new engine. They have to walk onto the factory floor, stop the assembly line, remove the old engine by hand, bolt the new one in, and restart the line. It is slow and prone to mistakes.

• CI/CD (The Automated Factory): The engineer drops a blueprint into an inbox (Azure Repos). A robot (Azure Pipelines) instantly detects the blueprint. The robot autonomously builds the engine (Docker build), tests it to ensure it won't explode (Unit Tests), walks onto the factory floor, and seamlessly swaps the engine while the car is still moving (Zero-downtime deployment). The engineer never leaves their desk.

4. The Azure DevOps Suite #

• Azure Boards: Like Jira or Trello. Used for Agile sprint planning and ticketing.

• Azure Repos: Like GitHub. Unlimited, private Git repository hosting.

• Azure Pipelines: The CI/CD engine that builds and deploys the code.

• Azure Artifacts: A package manager (like npm or NuGet) for sharing internal code libraries securely.

5. The CI/CD Pipeline Flow #

1. 1. Trigger: A developer merges code into the main branch in Azure Repos (or GitHub).

1. 2. Azure Pipelines Wakes Up: The webhook triggers the Pipeline.

1. 3. Step 1 (Test): Run automated .NET/Node.js unit tests. If they fail, STOP the pipeline.

1. 4. Step 2 (Build): Run docker build or dotnet publish to package the new code.

1. 5. Step 3 (Publish Artifact): Save the compiled code as an "Artifact".

1. 6. Step 4 (Deploy): The "Release" stage downloads the Artifact and securely pushes it to Azure App Service or AKS.

6. Anatomy of an azure-pipelines.yml #

trigger:
  - main

pool:
  vmImage: 'ubuntu-latest'

steps:
# Step 1: Install Node.js
- task: NodeTool@0
  inputs:
    versionSpec: '18.x'
  displayName: 'Install Node.js'

# Step 2: Build the code
- script: |
    npm install
    npm run build
  displayName: 'npm install and build'

# Step 3: Deploy to Azure App Service
- task: AzureRmWebAppDeployment@4
  inputs:
    ConnectionType: 'AzureRM'
    azureSubscription: 'MyServiceConnection'
    appType: 'webAppLinux'
    WebAppName: 'my-production-app'
    packageForLinux: '$(System.DefaultWorkingDirectory)/**/*.zip'

7. Mini Project: Conceptual Automated Deployment #

Step-by-Step Overview:

1. 1. Ensure your application code is committed to an Azure Repo or a GitHub repository.

1. 2. In Azure DevOps (dev.azure.com), navigate to Pipelines.

1. 3. Click Create Pipeline.

1. 4. Connect: Select where your code is (e.g., Azure Repos Git or GitHub).

1. 5. Select: Select your specific repository.

1. 6. Configure: Azure Pipelines is incredibly smart. It will scan your code, realize it is a Node.js app, and automatically generate a starter YAML file for you!

1. 7. Review: Review the generated azure-pipelines.yml file. Modify the "Deploy" task to point to your existing Azure App Service.

1. 8. Click Save and run.

1. 9. The Test: Go to your laptop, change a line of HTML, and git push origin main. Return to the Azure DevOps portal. You will see your pipeline executing live, successfully updating your live website without a single manual server login!

8. Real-World Scenarios #

9. Best Practices #

• Deployment Gates: In a true Enterprise Release pipeline, you don't deploy straight to Production. You deploy to a "Staging" environment. Then, you configure a "Pre-deployment Approval Gate". The pipeline literally pauses and sends an email to the QA Manager. The code will not deploy to Production until the manager clicks "Approve".

10. Common Mistakes #

• Service Connection Failures: When Azure DevOps reaches the "Deploy" step, it must authenticate to your Azure Subscription. Beginners often struggle with this. You must configure an Azure Resource Manager Service Connection within the DevOps project settings, which securely grants DevOps the RBAC permissions to modify your cloud resources.

11. Exercises #

1. 1. What is the fundamental security advantage of allowing an Azure Pipeline to handle deployments rather than allowing developers to deploy code from their local laptops?

1. 2. Explain the purpose of a "Pre-deployment Approval Gate" in an enterprise release pipeline.

12. FAQs #

13. Interview Questions #

• Q: Detail the architectural flow of a Continuous Deployment pipeline from a developer's git push to a live application update on Azure App Service, specifically highlighting the role of the Service Connection.

• Q: Explain the difference between Continuous Integration (CI) and Continuous Deployment (CD). Provide an example of a task that belongs exclusively in the CI phase versus the CD phase.

14. Summary #

15. Next Chapter Recommendation #