• Automation

  Pipeline

  A pipeline is an automated, ordered sequence of steps that builds, tests and ships your code every time it changes. Each step runs only if the previous one succeeds, so a single commit can flow from source control to a live environment without manual handoffs.

• CI/CD practices

  Pipeline as code

  Pipeline as code is the practice of defining a CI/CD pipeline in a version-controlled file (typically YAML or a DSL stored alongside the application code), so the build, test, and deployment workflow is reviewable, repeatable, and rolls forward and back with the rest of the repository - instead of being clicked together in a web UI that nobody can diff.

• Governance & compliance

  Policy as code

  Policy as code is the practice of expressing organisational rules - security controls, compliance requirements, cost limits, deployment safety checks - as version-controlled files that a machine can evaluate automatically, so a CI/CD pipeline can decide whether a change is allowed to merge or deploy instead of waiting for a human reviewer to read a wiki.