Deployment methods (Git, ZIP, CI/CD) in Azure - Step-by-Step Execution

Process Flow - Deployment methods (Git, ZIP, CI/CD)

Start Deployment

↓

Choose Method

↓

Git

↓

Pull code

↓

Build & Deploy

↓

Verify Deployment

↓

End

Deployment starts by choosing a method: Git, ZIP upload, or CI/CD pipeline, each leading to build and deploy steps, then verification.

Execution Sample

Azure

az webapp deployment source config-local-git --name MyApp --resource-group MyGroup
az webapp deployment source config-zip --src app.zip --name MyApp --resource-group MyGroup
az pipelines run --project MyGroup --name MyPipeline

These commands deploy an Azure web app using Git, ZIP upload, and triggering a CI/CD pipeline respectively.

Process Table

Step	Method	Action	Command/Process	Result
1	Git	Configure local Git deployment	az webapp deployment source config-local-git --name MyApp --resource-group MyGroup	Git URL provided for push
2	Git	Push code to Azure Git remote	git push azure master	Code received by Azure, triggers build
3	Git	Build and deploy app	Azure build service runs	App deployed and running
4	ZIP	Upload ZIP package	az webapp deployment source config-zip --src app.zip --name MyApp --resource-group MyGroup	ZIP uploaded and extracted
5	ZIP	Deploy extracted files	Azure deploys files	App deployed and running
6	CI/CD	Trigger pipeline run	az pipelines run --project MyGroup --name MyPipeline	Pipeline starts build and deploy
7	CI/CD	Pipeline builds and tests	Build and test steps execute	Build and tests pass
8	CI/CD	Pipeline deploys app	Deploy step executes	App deployed and running
9	All	Verify deployment	Check app URL or logs	App is live and functional

💡 Deployment completes after app is live and verified.

Status Tracker

Variable	Start	After Git Config	After Git Push	After ZIP Upload	After CI/CD Trigger	Final
Deployment State	Not started	Git URL ready	Code pushed	ZIP uploaded	Pipeline running	App live

Key Moments - 3 Insights

Why does pushing code to Git trigger deployment automatically?

Because Azure Git deployment is configured (see execution_table step 1), pushing code to the Azure Git remote triggers the build and deploy process automatically (step 2 and 3).

What happens after uploading a ZIP file for deployment?

After uploading the ZIP (step 4), Azure extracts the files and deploys them directly (step 5), so no separate build step is needed unless configured.

How does CI/CD pipeline deployment differ from Git or ZIP?

CI/CD pipelines (steps 6-8) include build and test stages before deployment, providing automation and quality checks, unlike direct Git or ZIP deployments.

Visual Quiz - 3 Questions

Look at the execution table, what is the deployment state after pushing code to Git?

A ZIP uploaded

B Git URL ready

C Code pushed

D Pipeline running

💡 Hint

Check variable_tracker column 'After Git Push' and execution_table step 2

At which step does the ZIP deployment extract and deploy files?

A Step 5

B Step 4

C Step 6

D Step 3

💡 Hint

Look at execution_table rows for ZIP method, steps 4 and 5

If the CI/CD pipeline fails tests, what happens to deployment?

A App is deployed anyway

B Deployment stops before deploy step

C ZIP upload is triggered

D Git push is required

💡 Hint

Refer to execution_table steps 7 and 8 where tests run before deploy

Concept Snapshot

Deployment methods in Azure:
- Git: Push code to Azure Git remote triggers build and deploy
- ZIP: Upload ZIP package, Azure extracts and deploys
- CI/CD: Pipeline automates build, test, deploy
Choose method based on automation needs and control
Verify deployment by checking app status

Full Transcript

This visual execution shows three Azure deployment methods: Git, ZIP, and CI/CD. Deployment starts by choosing a method. For Git, you configure local Git deployment, then push code to Azure, which triggers build and deploy automatically. For ZIP, you upload a ZIP file that Azure extracts and deploys directly. For CI/CD, you trigger a pipeline that builds, tests, and deploys the app. The execution table traces each step with commands and results. The variable tracker shows deployment state changes. Key moments clarify why Git push triggers deployment, what happens after ZIP upload, and how CI/CD adds testing before deploy. The quiz tests understanding of deployment states and steps. The snapshot summarizes key points for quick reference.

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