Release pipeline basics in Azure - Step-by-Step Execution

Process Flow - Release pipeline basics

Start Release Pipeline

↓

Fetch Artifacts

↓

Deploy to Environment

↓

Run Tests

↓

Approve Deployment?

No→Stop Pipeline

Yes↓

Deploy to Next Environment or Finish

↓

End

The release pipeline starts by fetching build artifacts, then deploys them to an environment, runs tests, waits for approval, and either stops or continues to the next environment until finished.

Execution Sample

Azure

Start pipeline
Fetch artifacts
Deploy to Dev
Run tests
Approve deployment
Deploy to Prod

This sequence shows a release pipeline deploying code first to a development environment, running tests, then after approval, deploying to production.

Process Table

Step	Action	Result	Next Step
1	Start pipeline	Pipeline started	Fetch artifacts
2	Fetch artifacts	Artifacts ready	Deploy to Dev
3	Deploy to Dev	Code deployed to Dev	Run tests
4	Run tests	Tests passed	Approve deployment
5	Approve deployment	Approval granted	Deploy to Prod
6	Deploy to Prod	Code deployed to Prod	End pipeline
7	End pipeline	Pipeline finished successfully	None

💡 Pipeline ends after successful deployment to production.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Pipeline Status	Not started	Artifacts fetched	Deployed to Dev	Tests passed	Approved	Deployed to Prod	Finished
Environment	None	None	Dev	Dev	Dev	Prod	Prod
Approval	Pending	Pending	Pending	Pending	Granted	Granted	Granted

Key Moments - 2 Insights

Why does the pipeline stop if approval is not granted?

Because the approval step controls whether deployment continues. As shown in step 5 of the execution_table, if approval is not granted, the pipeline stops to prevent unwanted deployments.

What happens if tests fail after deployment to Dev?

The pipeline would stop after the 'Run tests' step (step 4) because tests must pass to proceed. This prevents deploying faulty code to production.

Visual Quiz - 3 Questions

Look at the execution_table, what is the pipeline status after step 3?

A Deployed to Dev

B Artifacts fetched

C Tests passed

D Approved

💡 Hint

Check the 'Pipeline Status' row in variable_tracker after step 3.

At which step does the pipeline wait for approval?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Action' column in execution_table for the approval step.

If tests fail at step 4, what happens next?

A Pipeline continues to deploy to Prod

B Pipeline stops

C Pipeline retries tests automatically

D Pipeline skips approval

💡 Hint

Refer to key_moments about test failure consequences.

Concept Snapshot

Release pipeline basics:
- Starts by fetching build artifacts
- Deploys to an environment (e.g., Dev)
- Runs tests to verify deployment
- Waits for manual approval before next deployment
- Deploys to next environment or finishes
- Stops if tests fail or approval denied

Full Transcript

A release pipeline automates deploying code through stages. It begins by fetching the build artifacts. Then it deploys the code to a development environment. After deployment, it runs tests to ensure the code works. If tests pass, the pipeline waits for a manual approval. Once approved, it deploys to the production environment. The pipeline stops if tests fail or approval is not granted. This process ensures safe and controlled code releases.