yml904 B

Azure Pipelines Stages and Deployment Job

A three-stage Azure Pipelines definition with a build-number format expression, a variable group reference, stage conditions built from the expression functions, and a deployment job using the runOnce strategy against a named environment.

Config testing Config parsing Editor testing

Preview — first 45 linesyml

name: $(Date:yyyyMMdd)$(Rev:.r)

trigger:
  - main

variables:
  - name: vmImage
    value: ubuntu-latest
  - group: example-nonsecret-settings

stages:
  - stage: Build
    displayName: Build and package
    jobs:
      - job: Compile
        pool:
          vmImage: $(vmImage)
        steps:
          - script: make build
            displayName: Compile

  - stage: Test
    dependsOn: Build
    condition: succeeded()
    jobs:
      - job: Unit
        pool:
          vmImage: $(vmImage)
        steps:
          - script: make test

  - stage: Deploy
    dependsOn:
      - Build
      - Test
    condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/main'))
    jobs:
      - deployment: Rollout
        environment: production
        strategy:
          runOnce:
            deploy:
              steps:
                - script: echo "rolling out $(Build.BuildNumber)"

Specifications

System: Azure Pipelines
Stages: 3
Depends On Edges: 3
Deployment Jobs: 1
Strategy: runOnce
Build Number Format: true

Testing contract

Expected to pass

Scenario: Build the stage dependency graph and evaluate stage conditions for an Azure pipeline
Expected result: Three stages resolve with Deploy depending on both Build and Test, and the Deploy condition combines succeeded() with a branch equality check

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 Stages and Deployment Job” 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 · 904 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-stages.yml") as f:
    data = yaml.safe_load(f)
print(data)

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