Deployment methods (Git, ZIP, CI/CD) in Azure - Deep Dive

Overview - Deployment methods (Git, ZIP, CI/CD)

What is it?

Deployment methods are ways to move your application or website from your computer to a cloud service like Azure so people can use it. Git deployment uses a special code storage system to send updates. ZIP deployment sends a compressed file with your app. CI/CD automates the whole process to make deployments faster and less error-prone. These methods help keep your app live and updated smoothly.

Why it matters

Without deployment methods, updating apps would be slow, error-prone, and manual, causing downtime and unhappy users. These methods solve the problem by making updates reliable and quick. Imagine if every time you wanted to update your phone app, you had to do it by hand on each device. Deployment methods automate and simplify this for cloud apps, saving time and avoiding mistakes.

Where it fits

Before learning deployment methods, you should understand basic cloud concepts and how to write and test code locally. After this, you can learn about advanced automation, monitoring deployments, and scaling apps in the cloud.

Mental Model

Core Idea

Deployment methods are the bridges that safely and efficiently carry your app from your computer to the cloud where users can access it.

Think of it like...

It's like sending a package: Git deployment is like sending items through a trusted courier who tracks every change, ZIP deployment is like mailing a sealed box, and CI/CD is like having a robot pack and send your packages automatically whenever you add new items.

┌─────────────┐      ┌─────────────┐      ┌─────────────┐
│  Developer  │─────▶│ Deployment  │─────▶│   Azure     │
│  Local PC   │      │  Method     │      │  Cloud App  │
└─────────────┘      └─────────────┘      └─────────────┘
       │                   │                   │
       │                   │                   │
       │                   │                   │
   (Code)             (Git, ZIP, CI/CD)     (Live App)

Build-Up - 7 Steps

1

Foundation

Understanding Basic Deployment

Concept: Deployment means moving your app from your computer to a place where others can use it.

Imagine you built a website on your computer. To let friends see it, you need to put it on a server. Deployment is this process of copying your app files to that server so it runs there.

Result

Your app is now accessible to users through the internet.

Understanding deployment as simply moving your app to a server helps remove the mystery and shows why it is necessary.

2

Foundation

What is Git Deployment?

Concept: Git deployment uses a code version system to send your app to the cloud.

Git is like a notebook that tracks every change you make to your code. When you use Git deployment, you push your code changes to a remote place (like Azure). Azure then updates your app automatically with those changes.

Result

Your app updates whenever you push new code to the Git repository.

Knowing that Git deployment tracks changes and updates your app automatically helps you keep your app versions organized and safe.

3

Intermediate

How ZIP Deployment Works

🤔Before reading on: do you think ZIP deployment sends individual files or a single compressed file? Commit to your answer.

Concept: ZIP deployment sends your entire app as one compressed file to the cloud for deployment.

Instead of sending files one by one, ZIP deployment packages your app into a ZIP file. This file is uploaded to Azure, which then extracts it and runs your app. This method is simple and fast for small to medium apps.

Result

Your app is deployed quickly as a single package, reducing upload errors.

Understanding ZIP deployment as a single package upload helps you see why it can be faster and simpler than sending many files.

4

Intermediate

Introduction to CI/CD Pipelines

🤔Before reading on: do you think CI/CD requires manual steps or is fully automated? Commit to your answer.

Concept: CI/CD automates building, testing, and deploying your app whenever you make changes.

CI (Continuous Integration) means your code is automatically tested and combined whenever you update it. CD (Continuous Deployment) means your app is automatically sent to Azure after passing tests. Together, CI/CD pipelines reduce errors and speed up delivery.

Result

Your app updates automatically and reliably without manual intervention.

Knowing CI/CD automates the entire deployment process helps you build faster and safer apps.

5

Intermediate

Comparing Git, ZIP, and CI/CD

🤔Before reading on: which deployment method do you think is best for frequent updates? Commit to your answer.

Concept: Each deployment method has strengths and fits different needs.

Git deployment is great for developers who want version control and easy updates. ZIP deployment is simple for quick uploads without version tracking. CI/CD is best for teams needing automated testing and fast, reliable releases.

Result

You can choose the right deployment method based on your project size and update frequency.

Understanding the trade-offs between methods helps you pick the best tool for your app's needs.

6

Advanced

Setting Up CI/CD in Azure

🤔Before reading on: do you think setting up CI/CD requires coding or just configuration? Commit to your answer.

Concept: Azure provides tools to create CI/CD pipelines with minimal coding using visual editors and YAML files.

You connect your code repository (like GitHub) to Azure DevOps or Azure Pipelines. Then you define steps to build, test, and deploy your app automatically. Azure handles the rest, making deployment repeatable and consistent.

Result

Your app deploys automatically on every code change with tests ensuring quality.

Knowing Azure's CI/CD tools simplify automation encourages you to adopt best practices early.

7

Expert

Advanced CI/CD: Blue-Green and Canary Deployments

🤔Before reading on: do you think all deployments replace the old app instantly? Commit to your answer.

Concept: Advanced CI/CD uses strategies like blue-green and canary to deploy updates safely without downtime.

Blue-green deployment runs two identical environments: one live (blue) and one idle (green). New code deploys to green, tested, then traffic switches from blue to green. Canary deployment releases updates to a small user group first, then gradually to all users. These reduce risk and allow quick rollback.

Result

Your app updates with zero downtime and minimal user impact.

Understanding these strategies helps you build resilient, user-friendly deployment pipelines.

Under the Hood

Deployment methods work by transferring your app's files and instructions to Azure's servers. Git deployment uses a version control system to track changes and push updates. ZIP deployment uploads a compressed archive that Azure extracts and runs. CI/CD pipelines automate steps like building code, running tests, and deploying using scripts or visual workflows. Azure manages these processes with services like Azure DevOps and App Service, ensuring your app runs smoothly.

Why designed this way?

These methods evolved to solve problems of manual, error-prone deployments. Git deployment leverages existing version control tools developers already use. ZIP deployment offers a simple, universal way to upload apps. CI/CD was designed to automate and speed up delivery while improving quality through testing. Alternatives like manual FTP uploads were too slow and risky, so these methods became standard.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│   Developer   │──────▶│  Deployment   │──────▶│    Azure      │
│  Local Code   │       │   Method      │       │   Servers     │
└───────────────┘       └───────────────┘       └───────────────┘
        │                      │                       │
        │                      │                       │
        │                      │                       │
   (Git Push)             (ZIP Upload)           (CI/CD Pipeline)
        │                      │                       │
        ▼                      ▼                       ▼
  Version Control         Compressed File        Automated Build
  System Tracks          Sent and Extracted     Test and Deploy
  Changes               by Azure               Your App

Myth Busters - 4 Common Misconceptions

Quick: Does ZIP deployment track your code changes automatically? Commit to yes or no.

Common Belief: ZIP deployment automatically tracks and manages code versions like Git.

Reality: ZIP deployment simply uploads a compressed file; it does not track changes or versions.

Why it matters: Believing ZIP tracks versions can lead to lost changes and confusion about app state.

Quick: Is CI/CD only useful for large teams? Commit to yes or no.

Common Belief: CI/CD pipelines are only necessary for big teams or complex projects.

Reality: CI/CD benefits all projects by automating testing and deployment, reducing errors even for small teams.

Why it matters: Ignoring CI/CD can cause avoidable bugs and slow updates, even in small projects.

Quick: Does Git deployment require manual uploads of files? Commit to yes or no.

Common Belief: Git deployment means manually uploading files to Azure after pushing code.

Reality: Git deployment automatically updates Azure apps when you push code; no manual uploads needed.

Why it matters: Misunderstanding this wastes time and causes deployment errors.

Quick: Do all deployments instantly replace the old app without overlap? Commit to yes or no.

Common Belief: Deployments always replace the old app instantly, causing downtime.

Reality: Advanced methods like blue-green and canary deployments allow zero downtime by gradual or parallel updates.

Why it matters: Not using these methods can cause user disruptions and lost revenue.

Expert Zone

1

CI/CD pipelines can integrate security scans to catch vulnerabilities before deployment, a practice called DevSecOps.

2

Azure supports deployment slots allowing you to test new versions in a live environment before swapping to production.

3

Automated rollbacks in CI/CD pipelines can revert to previous stable versions instantly if errors are detected.

When NOT to use

For very simple or one-time deployments, manual ZIP uploads may be sufficient and faster. If your app does not change often, full CI/CD automation might be unnecessary overhead. Alternatives include manual FTP or Azure Portal uploads for quick fixes.

Production Patterns

Teams use Git deployment combined with Azure DevOps pipelines to automate testing and deployment. Blue-green deployments are common for critical apps needing zero downtime. Canary releases help test new features with a subset of users before full rollout.

Connections

Version Control Systems

Deployment methods like Git deployment build directly on version control concepts.

Understanding version control deeply helps grasp how deployment tracks and manages app changes.

Automation in Manufacturing

CI/CD pipelines are similar to automated assembly lines that build, test, and package products without human intervention.

Seeing CI/CD as automation helps appreciate its role in speeding up and improving software delivery.

Supply Chain Logistics

Deployment methods manage the flow of software from development to users, like logistics manage goods from factory to customer.

Knowing supply chain principles clarifies why deployment needs reliability, tracking, and risk management.

Common Pitfalls

#1 Uploading incomplete ZIP files causing deployment failures.

Wrong approach:

Uploading a ZIP file before compressing all necessary app files, or with missing dependencies.

Correct approach:

Ensure the ZIP file contains all app files and dependencies before uploading to Azure.

Root cause:

Not verifying the ZIP contents leads to broken apps after deployment.

#2 Skipping tests in CI/CD pipelines causing buggy releases.

Wrong approach:

Configuring CI/CD to deploy immediately without running automated tests.

Correct approach:

Set up CI/CD pipelines to run tests and only deploy if tests pass successfully.

Root cause:

Ignoring testing steps risks deploying broken or unstable code.

#3 Manually editing live apps instead of using deployment methods.

Wrong approach:

Logging into Azure and changing files directly on the server.

Correct approach:

Use Git, ZIP, or CI/CD deployment methods to update apps consistently and safely.

Root cause:

Lack of understanding deployment best practices leads to inconsistent app states and errors.

Key Takeaways

Deployment methods move your app from your computer to the cloud so users can access it.

Git deployment uses version control to track and update your app automatically.

ZIP deployment sends your app as a single compressed file for simple uploads.

CI/CD pipelines automate building, testing, and deploying your app to improve speed and reliability.

Advanced deployment strategies like blue-green and canary reduce downtime and risk during updates.

Practice

1. Which deployment method in Azure allows you to push your app code directly from your source code repository?

easy

A. Manual file upload

B. ZIP deployment

C. FTP deployment

D. Git deployment

Solution

1. Step 1: Understand Git deployment

   Git deployment connects your Azure app directly to your Git repository, pushing code changes automatically.

2. Step 2: Compare with other methods

   ZIP deployment uploads a packaged file, manual upload and FTP are manual and not direct from repo.

3. Final Answer:

   Git deployment -> Option D

4. Quick Check:

   Direct repo push = Git deployment [OK]

Hint: Git deployment means pushing code from your repo directly [OK]

Common Mistakes:

• Confusing ZIP deployment with Git deployment
• Thinking FTP is automated from repo
• Assuming manual upload is Git-based

2. Which of the following is the correct Azure CLI command to deploy a ZIP package to an Azure Web App named myapp in resource group mygroup?

easy

A. az webapp deploy zip --resource-group mygroup --app-name myapp --file app.zip

B. az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip

C. az deployment zip --resource-group mygroup --webapp myapp --package app.zip

D. az webapp deployment upload-zip --resource-group mygroup --name myapp --zip-file app.zip

Solution

1. Step 1: Identify correct Azure CLI syntax for ZIP deployment

   The official command is az webapp deployment source config-zip with parameters for resource group, app name, and source ZIP file.

2. Step 2: Check options for syntax correctness

   az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip matches the correct command and parameters exactly; others use incorrect commands or flags.

3. Final Answer:

   az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip -> Option B

4. Quick Check:

   Correct CLI command for ZIP deploy = az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip [OK]

Hint: Remember 'config-zip' is the key command for ZIP deploy [OK]

Common Mistakes:

• Using wrong command verbs like 'deploy' or 'upload-zip'
• Mixing parameter names like --app-name vs --name
• Forgetting to specify the source ZIP file with --src

3. Given this Azure DevOps pipeline snippet for CI/CD deployment:

trigger:
  branches:
    include:
      - main

steps:
- task: AzureWebApp@1
  inputs:
    azureSubscription: 'MyAzureSub'
    appName: 'myapp'
    package: '$(System.DefaultWorkingDirectory)/drop/app.zip'

What happens when you push code to the main branch?

medium

A. The pipeline triggers and deletes the Azure Web App

B. The pipeline triggers but does not deploy anything

C. The pipeline triggers and deploys the ZIP package to the Azure Web App

D. The pipeline does not trigger on main branch pushes

Solution

1. Step 1: Analyze the trigger section

   The pipeline triggers on pushes to the main branch as specified in the trigger include list.

2. Step 2: Understand the deployment task

   The AzureWebApp@1 task deploys the ZIP package located at the specified path to the Azure Web App named 'myapp'.

3. Final Answer:

   The pipeline triggers and deploys the ZIP package to the Azure Web App -> Option C

4. Quick Check:

   Push to main triggers deploy task = The pipeline triggers and deploys the ZIP package to the Azure Web App [OK]

Hint: Trigger on main means pipeline runs and deploys ZIP package [OK]

Common Mistakes:

• Assuming pipeline triggers on other branches
• Thinking deployment task does nothing
• Confusing deployment with deletion

4. You configured a CI/CD pipeline to deploy your app, but the deployment fails with an authentication error. What is the most likely cause?

medium

A. Incorrect Azure subscription service connection in the pipeline

B. ZIP package file is missing from the build artifacts

C. App name in the pipeline does not match the Azure Web App

D. Pipeline trigger is set to the wrong branch

Solution

1. Step 1: Identify cause of authentication error

   Authentication errors usually mean the pipeline cannot access Azure resources due to wrong or missing service connection credentials.

2. Step 2: Evaluate other options

   Missing ZIP or wrong app name cause deployment errors but not authentication errors; wrong trigger prevents pipeline start.

3. Final Answer:

   Incorrect Azure subscription service connection in the pipeline -> Option A

4. Quick Check:

   Auth error = service connection issue [OK]

Hint: Auth errors usually mean bad Azure service connection [OK]

Common Mistakes:

• Blaming missing ZIP for authentication errors
• Confusing app name mismatch with auth failure
• Assuming trigger issues cause auth errors

5. You want to automate deployment so that when code is pushed to GitHub, it builds, tests, and deploys your app to Azure automatically. Which combination of deployment methods should you use?

hard

A. CI/CD pipeline connected to GitHub with automated build and deploy steps

B. Manual ZIP deployment after pushing code to GitHub

C. FTP deployment triggered by GitHub webhook

D. Git deployment directly from GitHub without build or test

Solution

1. Step 1: Understand automation needs

   Automating build, test, and deploy requires a CI/CD pipeline connected to the source repository.

2. Step 2: Compare deployment methods

   Manual ZIP and FTP are manual or partial automation; Git deployment pushes code but lacks build/test automation.

3. Final Answer:

   CI/CD pipeline connected to GitHub with automated build and deploy steps -> Option A

4. Quick Check:

   Full automation = CI/CD pipeline [OK]

Hint: Full automation needs CI/CD pipeline linked to GitHub [OK]

Common Mistakes:

• Thinking Git deployment automates build and test
• Assuming FTP can automate deployment fully
• Using manual ZIP deploy for automation