Multi-stage Azure Devops Pipeline with cross-platform matrix

azure-pipelines.yml

# Determines which branch(es) will cause a CI build to be started
trigger:
- master

# Stages precede strategy, in other words each stage can contain a strategy (or multiple or none)
# Full run-cylce described here: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/runs?view=azure-devops
stages:
- stage: Prepare
  jobs:
  - job:
    pool:
      vmImage: 'ubuntu-16.04'
    steps:
    - powershell: |
        "OS = $($env:AGENT_OS)" | Out-Host
      displayName: 'Dummy Prepare Step'

- stage: Build
  dependsOn: Prepare
  jobs:
  - job:
    pool:
      vmImage: 'windows-2019'
    steps:
    - powershell: |
        "OS = $($env:AGENT_OS)" | Out-Host
      displayName: 'Dummy Build Step'

- stage: Test
  dependsOn: Build
  jobs:
  - job:
    strategy:
      matrix:
        Linux:
          imageName: 'ubuntu-16.04'
        Mac:
          imageName: 'macOS-10.14'
        Windows:
          imageName: 'windows-2019'
        Code Coverage:
          imageName: 'windows-2019'
        Script Analysis:
          imageName: 'windows-2019'
    pool:
      vmImage: $(imageName)
    steps:
    - powershell: |
        "OS = $($env:AGENT_OS)" | Out-Host
      displayName: 'Dummy Test Step'

- stage: Document
  dependsOn: Test
  jobs:
  - job:
    pool:
      vmImage: 'windows-2019'
    steps:
    - powershell: |
        "OS = $($env:AGENT_OS)" | Out-Host
      displayName: 'Dummy Document Step'

- stage: Release
  dependsOn: Document
  jobs:
  - job:
    pool:
      vmImage: 'windows-2019'
    steps:
    - powershell: |
        "OS = $($env:AGENT_OS)" | Out-Host
      displayName: 'Dummy Release Step'

This Azure Devops Pipeline creates 5 stages where the cross-platform matrix in the Test stage will generate 5 separate jobs for that stage, one for each platform.

Please note that you MUST enable the preview feature Multi-stage pipelines in your Azure Devops user profile for this to work.

It will look like this when running the pipeline:

When the run has completed it will look like this: