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.