azure
1 guardrails, all at version v1.
| Guardrail | Default severity | What it checks |
|---|---|---|
azure/job-timeout-set | info | Every job declares a timeout, and none of them asks for the maximum, so a hung job is stopped instead of holding an agent. |
Shared inputs
Every azure guardrail declares these inputs. Individual guardrails can add their own.
| Input | Description | Default |
|---|---|---|
pipelines | Comma separated globs naming the Azure Pipelines definitions to read. | azure-pipelines*.yml,azure-pipelines*.yaml |
Shared collectors
Every azure guardrail receives the facts these collectors gather. Individual guardrails can ask for more collectors of their own.
| Collector | Gathers |
|---|---|
azure | The Azure Pipelines YAML the repository carries, read as Azure writes it: what starts a run, the stages and jobs it declares, the pool each job lands on and how long it may run, and every task a step reaches for with the version it asks for, alongside the macro, template and runtime expressions a script interpolates. Names and shapes only, never a secret, an input value or a variable value. |
You configure every guardrail in this category the same way, in the guardrails.checks array of buildnote.json. Configuring guardrails lists every option, and Guardrails lets you search the whole library.