Skip to content

Pipelines

A pipeline is the definition of a flow of jobs: when it starts, which jobs run, and how the results are handled.

The standard four

  • check: runs when a change is created or updated. Results are reported on the change; nothing is merged
  • gate: the checkpoint before a merge. Only changes that pass are merged (see “How gating works”)
  • post: runs after a merge. Work that assumes the merge, such as publishing and delivery, lives here
  • periodic: runs on a schedule. Whole-system health checks and recovery of missed work live here

The names are set in configuration; these four are the conventional shape. You can add pipelines, or split a gate into stages, to fit the purpose.

How Aether splits them

Aether keeps the gate for development merges and the gate for promotion to qa as separate pipelines. Development changes enter through the first gate; promotion proceeds with its own conditions and its own flow. The promotion flow itself is on the “promotion flow” page.

Changing a flow

When something runs, and in what order, is the pipeline definition’s business. You can change the flow without touching the jobs’ contents (the procedures).