Azure Pipelines overview - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Azure Pipelines?

Azure Pipelines is a cloud service that helps you automatically build, test, and deploy your code to any platform or cloud.

beginner

What does CI/CD stand for in Azure Pipelines?

CI/CD stands for Continuous Integration and Continuous Delivery. It means automatically combining code changes and delivering them quickly and safely.

intermediate

What are the main parts of an Azure Pipeline?

The main parts are: 1) Build pipeline - compiles and tests code, 2) Release pipeline - deploys the app to environments like testing or production.

beginner

How does Azure Pipelines connect to your code?

It connects to your code stored in repositories like GitHub, Azure Repos, or Bitbucket to automatically run builds and deployments when code changes.

beginner

Why use Azure Pipelines instead of manual deployment?

Azure Pipelines saves time, reduces errors, and ensures your app is tested and deployed the same way every time without manual steps.

What is the primary purpose of Azure Pipelines?

A To automate building, testing, and deploying code

B To store large files in the cloud

C To monitor website traffic

D To manage user accounts

Azure Pipelines automates the process of building, testing, and deploying code.

Which of these is NOT a code repository Azure Pipelines can connect to?

A Microsoft Word

B Azure Repos

C Bitbucket

D GitHub

Microsoft Word is not a code repository; Azure Pipelines connects to GitHub, Azure Repos, and Bitbucket.

What does Continuous Integration (CI) mean?

A Manually testing code after deployment

B Deploying code only once a year

C Writing code without testing

D Automatically combining code changes and testing them

Continuous Integration means automatically combining code changes and running tests to catch issues early.

Which pipeline in Azure Pipelines is responsible for deploying your app?

A Test pipeline

B Build pipeline

C Release pipeline

D Storage pipeline

The Release pipeline handles deploying your app to different environments.

What is a key benefit of using Azure Pipelines?

A Manual deployment control

B Faster and consistent app delivery

C Increased paperwork

D Slower testing process

Azure Pipelines helps deliver apps faster and more consistently by automating builds and deployments.

Explain what Azure Pipelines does and why it is useful.

Think about how it helps developers deliver code faster and safer.

Describe the difference between a build pipeline and a release pipeline in Azure Pipelines.

One prepares the code, the other sends it out.

Practice

1. What is the main purpose of Azure Pipelines?

easy

A. To automate building, testing, and deploying code

B. To store large amounts of data

C. To create virtual machines

D. To monitor network traffic

Solution

1. Step 1: Understand Azure Pipelines role

   Azure Pipelines automate the process of building, testing, and deploying code changes.

2. Step 2: Compare options with purpose

   Options B, C, and D describe other Azure services, not pipelines.

3. Final Answer:

   To automate building, testing, and deploying code -> Option A

4. Quick Check:

   Azure Pipelines = automate build/test/deploy [OK]

Hint: Remember pipelines automate code workflows [OK]

Common Mistakes:

• Confusing pipelines with storage services
• Thinking pipelines create virtual machines
• Mixing pipelines with monitoring tools

2. Which file format is commonly used to define Azure Pipelines?

easy

A. .json

B. .txt

C. .xml

D. .yaml

Solution

1. Step 1: Identify pipeline definition format

   Azure Pipelines use YAML files to define build and deployment steps.

2. Step 2: Eliminate other formats

   JSON, XML, and TXT are not standard for pipeline definitions in Azure.

3. Final Answer:

   .yaml -> Option D

4. Quick Check:

   Pipeline config = YAML file [OK]

Hint: YAML files define pipeline steps clearly [OK]

Common Mistakes:

• Choosing JSON instead of YAML
• Confusing XML with pipeline config
• Thinking plain text files define pipelines

3. Given this YAML snippet in an Azure Pipeline:

trigger:
  branches:
    include:
      - main

steps:
- script: echo Hello, world!

What happens when you push code to the main branch?

medium

A. The pipeline fails due to syntax error

B. The pipeline ignores the push

C. The pipeline runs and prints 'Hello, world!'

D. The pipeline runs but does nothing

Solution

1. Step 1: Understand trigger configuration

   The pipeline triggers on pushes to the 'main' branch as specified.

2. Step 2: Analyze steps section

   The single step runs a script that echoes 'Hello, world!'.

3. Final Answer:

   The pipeline runs and prints 'Hello, world!' -> Option C

4. Quick Check:

   Trigger on main runs echo script [OK]

Hint: Trigger on branch runs defined script [OK]

Common Mistakes:

• Assuming pipeline ignores main branch
• Thinking pipeline does nothing on trigger
• Believing syntax error exists in snippet

4. You wrote this YAML for Azure Pipelines but it never triggers:

trigger:
  branches:
    exclude:
      - main

steps:
- script: echo Build started

What is the likely problem?

medium

A. The pipeline excludes the main branch, so pushes to main don't trigger it

B. The script syntax is incorrect

C. The trigger keyword is misspelled

D. The pipeline requires a separate build agent

Solution

1. Step 1: Review trigger exclude setting

   The pipeline excludes the 'main' branch, so pushes to 'main' won't start it.

2. Step 2: Check other parts

   The script syntax and trigger keyword are correct; no build agent issue is indicated.

3. Final Answer:

   The pipeline excludes the main branch, so pushes to main don't trigger it -> Option A

4. Quick Check:

   Exclude main branch stops trigger [OK]

Hint: Exclude means branch won't trigger pipeline [OK]

Common Mistakes:

• Thinking script syntax is wrong
• Assuming trigger keyword typo
• Believing build agent is missing

5. You want to run tests only when code is pushed to the develop branch and deploy only when code is pushed to main. How should you configure triggers in your Azure Pipelines YAML?

hard

A. Use a single pipeline triggered on both branches and run all steps always

B. Use two separate pipelines: one triggered on 'develop' for tests, another on 'main' for deploy

C. Trigger only on 'main' and manually run tests

D. Trigger only on 'develop' and deploy manually

Solution

1. Step 1: Understand branch-specific triggers

   Running tests and deploy on different branches requires separate triggers.

2. Step 2: Choose pipeline structure

   Two pipelines allow independent triggers and steps per branch, matching requirements.

3. Step 3: Evaluate other options

   Single pipeline running all steps always doesn't separate concerns; manual runs reduce automation benefits.

4. Final Answer:

   Use two separate pipelines: one triggered on 'develop' for tests, another on 'main' for deploy -> Option B

5. Quick Check:

   Separate pipelines for branch-specific tasks [OK]

Hint: Separate pipelines for different branch tasks [OK]

Common Mistakes:

• Using one pipeline for all branches without conditions
• Triggering only on main and skipping tests automation
• Triggering only on develop and missing deploy automation