Skip to content
Novus Examples
yml866 B

Azure Pipelines Template Expressions and Parameters

Compile-time template expressions: an `${{ each }}` loop over an object parameter, an `${{ if }}` conditional insertion, an `extends` template, and a step template with arguments. These resolve before runtime, which template-aware linters must model.

Config testingConfig parsingEditor testing
Preview — first 37 linesyml
parameters:
  - name: targets
    type: object
    default:
      - name: linux
        image: ubuntu-latest
      - name: windows
        image: windows-latest
  - name: runIntegration
    type: boolean
    default: false
  - name: verbosity
    type: string
    default: normal
    values:
      - quiet
      - normal
      - detailed

extends:
  template: templates/base-pipeline.yml
  parameters:
    verbosity: ${{ parameters.verbosity }}

jobs:
  - ${{ each target in parameters.targets }}:
      - job: build_${{ target.name }}
        pool:
          vmImage: ${{ target.image }}
        steps:
          - template: templates/steps-build.yml
            parameters:
              platform: ${{ target.name }}
          - ${{ if eq(parameters.runIntegration, true) }}:
              - script: make integration
                displayName: Integration tests

Specifications

System
Azure Pipelines
Parameters
3
Parameter Types
object, boolean, string
Compile Time Expressions
each, if
Template References
2

Testing contract

Expected to pass
Scenario
Expand Azure Pipelines compile-time template expressions before any runtime evaluation
Expected result
The each loop generates 2 jobs, the if block is omitted while runIntegration defaults to false, and both template references are recorded as dependencies

What is a .yml file?

YML is an alternate file extension for YAML, a human-readable data-serialization format based on indentation, key-value mappings, and lists. The content and parsing rules are identical to .yaml; only the extension differs. It is widely used for CI and application configuration files.

How to use this file

Use an example YML file to test that config loaders treat .yml and .yaml identically, and to exercise indentation, comment, and multi-document parsing.

How to use this file for testing

“Azure Pipelines Template Expressions and Parameters” is a deterministic Novus Examples fixture for Config testing, Config parsing, Editor testing. TOML, INI, YAML, .env, and dotfile configuration samples with nested sections and typed values — for testing config parsers, loaders, and environment tooling.

Documented properties for this file: YML · 866 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Pipeline and infrastructure fixtures are inert configuration: steps reference fictional images and scripts, and nothing here executes. Run your linter, schema validator, migrator, or policy engine against them, and expect the deprecated-syntax and intentionally invalid variants to be rejected.

Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.

Code examples

import yaml  # pip install pyyaml

with open("azure-pipelines-templates.yml") as f:
    data = yaml.safe_load(f)
print(data)

Related files

Generated by generation/pipelines.py. Free for any use, no attribution required — license.