Release pipeline basics in Azure - Mini Project: Build & Apply

Release pipeline basics

📖 Scenario: You work in a software team that wants to automate the deployment of their web app. To do this, you will create a simple release pipeline in Azure DevOps. This pipeline will take the built app and deploy it to a test environment automatically.

🎯 Goal: Build a basic Azure DevOps release pipeline with one stage that deploys an app artifact to a test environment.

📋 What You'll Learn

Create a release pipeline definition with a name

Add an artifact source named exactly 'drop'

Add a stage named exactly 'Test'

Configure the stage to deploy the artifact

💡 Why This Matters

🌍 Real World

Release pipelines automate deploying software to environments, saving time and reducing errors.

💼 Career

Understanding release pipelines is essential for DevOps engineers and cloud infrastructure specialists to manage software delivery.

1

Create the release pipeline definition

Create a YAML variable called releasePipeline that defines a release pipeline with the name 'MyReleasePipeline' and an empty stages list.

Azure

# Your code here

Hint

Use a Python dictionary with keys 'name', 'artifacts', and 'stages'.

2

Add an artifact source

Add an artifact to releasePipeline['artifacts'] with the exact name 'drop' and type 'Build'.

Azure

releasePipeline = {
    'name': 'MyReleasePipeline',
    'artifacts': [],
    'stages': []
}
# Add an artifact with name 'drop' and type 'Build' below

Hint

Add a dictionary with keys 'alias' and 'type' inside the 'artifacts' list.

3

Add a deployment stage

Add a stage to releasePipeline['stages'] with the exact name 'Test' and a job that deploys the artifact named 'drop'.

Azure

releasePipeline = {
    'name': 'MyReleasePipeline',
    'artifacts': [
        {'alias': 'drop', 'type': 'Build'}
    ],
    'stages': []
}
# Add a stage named 'Test' with a deployment job for artifact 'drop' below

Hint

The stage should have a 'jobs' list with one deployment job referencing the 'drop' artifact.

4

Complete the release pipeline configuration

Add a trigger key to releasePipeline with the value {'batch': False} to disable batch triggering.

Azure

releasePipeline = {
    'name': 'MyReleasePipeline',
    'artifacts': [
        {'alias': 'drop', 'type': 'Build'}
    ],
    'stages': [
        {
            'name': 'Test',
            'jobs': [
                {
                    'deployment': {
                        'artifactAlias': 'drop',
                        'environment': 'TestEnvironment'
                    }
                }
            ]
        }
    ]
}
# Add a trigger key with batch set to false below

Hint

The trigger key controls how releases start automatically.

Practice

1. What is the main purpose of a release pipeline in Azure DevOps?

easy

A. To monitor user activity on a website

B. To automate the delivery of applications through different stages

C. To write code for applications

D. To store application data securely

Solution

1. Step 1: Understand the role of a release pipeline

   A release pipeline automates the process of delivering software through stages like testing and production.

2. Step 2: Identify the correct purpose

   Among the options, only automating delivery matches the release pipeline's function.

3. Final Answer:

   To automate the delivery of applications through different stages -> Option B

4. Quick Check:

   Release pipeline = automate delivery [OK]

Hint: Release pipelines automate app delivery stages [OK]

Common Mistakes:

• Confusing release pipeline with coding or monitoring tools
• Thinking it stores data instead of deploying apps

2. Which syntax correctly defines a stage in an Azure release pipeline YAML?

easy

A. stage:
- Build
jobs: []

B. jobs:
- stage: Build

C. stages:
Build:
jobs: []

D. stages:
- stage: Build
jobs: []

Solution

1. Step 1: Review YAML structure for stages

   In Azure pipelines, stages are defined under 'stages:' as a list with '- stage:' entries.

2. Step 2: Match correct syntax

   stages: - stage: Build jobs: [] correctly uses 'stages:' followed by '- stage: Build' and an empty jobs list.

3. Final Answer:

   stages: - stage: Build jobs: [] -> Option D

4. Quick Check:

   Stages list starts with 'stages:' and '- stage:' [OK]

Hint: Stages use 'stages:' then '- stage:' list items [OK]

Common Mistakes:

• Using singular 'stage:' instead of 'stages:'
• Placing 'stage' inside 'jobs' incorrectly
• Incorrect indentation or list syntax

3. Given this YAML snippet in a release pipeline:

stages:
  - stage: Test
    jobs:
      - job: RunTests
        steps:
          - script: echo Testing

What will be the output when this pipeline runs?

medium

A. It will print 'Testing' in the job logs

B. It will print 'echo Testing' literally

C. No output will be shown

D. The pipeline will fail due to syntax error

Solution

1. Step 1: Understand the script step in pipeline

   The 'script' step runs the command given, here 'echo Testing', which prints 'Testing'.

2. Step 2: Predict output

   Since the script runs successfully, the output 'Testing' appears in the job logs.

3. Final Answer:

   It will print 'Testing' in the job logs -> Option A

4. Quick Check:

   Script runs command, prints output [OK]

Hint: Script steps run commands and show output [OK]

Common Mistakes:

• Thinking script prints the command text instead of output
• Assuming syntax error without checking YAML correctness
• Expecting no output from script step

4. You have this YAML snippet in a release pipeline:

stages:
  - stage: Deploy
    jobs:
      - job: DeployJob
        steps:
          - script: echo Deploying
          - script: echo Done
        dependsOn: Build

What is wrong with this pipeline configuration?

medium

A. 'dependsOn' should be inside the stage, not inside jobs

B. 'dependsOn' must be a job, not a stage

C. The 'steps' section cannot have multiple scripts

D. The 'jobs' keyword is not allowed inside stages

Solution

1. Step 1: Locate 'dependsOn' usage

   'dependsOn' controls stage dependencies and must be placed at the stage level, not inside jobs.

2. Step 2: Identify correct placement

   In the snippet, 'dependsOn: Build' is incorrectly placed inside the job, it should be directly under the stage.

3. Final Answer:

   'dependsOn' should be inside the stage, not inside jobs -> Option A

4. Quick Check:

   'dependsOn' belongs to stage level [OK]

Hint: 'dependsOn' goes under stage, not job [OK]

Common Mistakes:

• Placing 'dependsOn' inside jobs instead of stages
• Thinking 'dependsOn' applies to jobs only
• Believing multiple scripts in steps is invalid

5. You want to create a release pipeline with two stages: Build and Deploy. Deploy should only run if Build succeeds. Which YAML snippet correctly sets this up?

hard

A. stages:
- stage: Build
jobs:
- job: BuildJob
steps:
- script: echo Building
- stage: Deploy
jobs:
- job: DeployJob
steps:
- script: echo Deploying

B. stages:
- stage: Build
dependsOn: Deploy
jobs:
- job: BuildJob
steps:
- script: echo Building
- stage: Deploy
jobs:
- job: DeployJob
steps:
- script: echo Deploying

C. stages:
- stage: Build
jobs:
- job: BuildJob
steps:
- script: echo Building
- stage: Deploy
dependsOn: Build
jobs:
- job: DeployJob
steps:
- script: echo Deploying

D. stages:
- stage: Deploy
dependsOn: Build
jobs:
- job: DeployJob
steps:
- script: echo Deploying
- stage: Build
jobs:
- job: BuildJob
steps:
- script: echo Building

Solution

1. Step 1: Understand stage dependencies

   To run Deploy only after Build succeeds, Deploy stage must depend on Build.

2. Step 2: Check YAML for correct 'dependsOn'

   stages: - stage: Build jobs: - job: BuildJob steps: - script: echo Building - stage: Deploy dependsOn: Build jobs: - job: DeployJob steps: - script: echo Deploying places 'dependsOn: Build' under Deploy stage, correctly setting the dependency.

3. Step 3: Verify order and jobs

   Build stage is first, Deploy second, with proper jobs and steps defined.

4. Final Answer:

   Correctly sets Deploy to depend on Build -> Option C

5. Quick Check:

   'dependsOn' on Deploy stage = correct dependency [OK]

Hint: Use 'dependsOn' on Deploy stage to wait for Build [OK]

Common Mistakes:

• Reversing 'dependsOn' causing wrong execution order
• Omitting 'dependsOn' so stages run in parallel
• Placing stages in wrong order without dependencies