Skip to content
Source on GitHubVisitors

Azure DevOps pipeline

Read an Azure DevOps pipeline by stage, job and step, opening one level at a time.

Diagram · origin tag azure-devops/pipeline · Infrastructure, network & cloud diagrams

Availability

Availability per host
HostStateHow to get it
StandalonePrototypeNot yet released
DesktopPrototypeNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Azure DevOps pipeline diagram, read at three levels: stages, the jobs inside an opened stage, and the steps inside an opened job (one element per step in declared order, no edges - steps are a sequence and not a graph). Opening either level is a menu entry on the element; there is no keyboard path for expansion at either level. Both levels push add and remove deltas rather than the `Group`/`Ungroup` actions the archived requirement named, deliberately and for the reasoning at `PipelineElementMapper.cs:87`; a change there would cover both levels at once

Why a specialized view helps

Pipeline YAML nests stages, jobs and steps inside templates; drilling down one level at a time keeps a long pipeline readable.

File formats

Not described yet.

Screenshots

The stage graph left-to-right with its dependency edges. Nothing selected.

Standalone, at a8616b3

What is visible: The stage graph left-to-right with its dependency edges. Nothing selected.

Why it matters: The whole pipeline reads left to right as stages and the dependencies between them, so the order of a run and where it fans out, here to staging and production, is clear without reading the YAML.

Licence: Apache-2.0

Background

Focus areas

Sources