CircleCI Workflow Matrix with Exclude
A CircleCI workflow matrix across three operating systems and two Go versions with one exclusion, plus a tag filter regex. Six combinations minus one is five jobs, documented so an expansion can be scored exactly.
version: 2.1
jobs:
compile:
parameters:
os:
type: string
go:
type: string
docker:
- image: registry.example.invalid/ci/go:<< parameters.go >>
steps:
- checkout
- run: go build ./...
workflows:
cross-build:
jobs:
- compile:
name: compile-<< matrix.os >>-<< matrix.go >>
matrix:
parameters:
os: [linux, darwin, windows]
go: ["1.22", "1.23"]
exclude:
- os: windows
go: "1.22"
filters:
tags:
only: /^v.*/
Specifications
- System
- CircleCI
- Base Combinations
- 6
- Excluded
- 1
- Final Combinations
- 5
- Tag Filter Regex
- true
Testing contract
Expected to pass- Scenario
- Expand a CircleCI workflow matrix that carries an exclude list and a tag filter
- Expected result
- The expansion yields exactly 5 jobs and the windows/1.22 combination is absent
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
“CircleCI Workflow Matrix with Exclude” 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 · 613 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("circleci-matrix-workflow.yml") as f:
data = yaml.safe_load(f)
print(data)Related files
- ymlCircleCI Config with Cache and WorkspaceA CircleCI 2.1 config with a two-job workflow, a fallback cache-key list, workspace persistence between jobs, and a test-results store. The baseline the other CircleCI fixtures vary from.
- ymlCircleCI Orbs and Named ExecutorsCircleCI orbs and reusable named executors: two orb imports, two executors at different resource classes, an orb-provided step, and a branch filter combining an exact name with a regex.
- ymlCircleCI Reusable Commands and ParametersA reusable CircleCI command with string and boolean parameters, a conditional `when` step, and a job parameterised by an enum expanded through a workflow matrix. Exercises CircleCI's << >> template syntax, which is not YAML and not Jinja.
- yamlArgo CD Application with Sync PolicyAn Argo CD Application with automated sync, prune and self-heal, retry backoff, sync options, and an ignoreDifferences rule that exempts replica counts from drift detection. All Git and cluster endpoints are example.invalid.
- yamlArgo CronWorkflow ScheduleAn Argo CronWorkflow wrapping an inline workflowSpec: a cron schedule with an explicit timezone, Replace concurrency, history limits, and a suspend flag. Nested-spec shape that flat schedule extractors miss.
- ymlAzure Pipelines Matrix StrategyAzure's named-leg matrix form, where each leg is a mapping of variables rather than an axis product: three Python legs, a maxParallel cap, a job timeout, and a JUnit results publish step that runs on failure too.
Generated by generation/pipelines.py. Free for any use, no attribution required — license.