Pipeline Workspace

Go up to Terms and Definitions

A Pipeline Workspace is the controlled file and execution context in which a build or deployment pipeline retrieves inputs, composes baselines, performs lifecycle operations, and records intermediate and final artefacts.

The Pipeline Workspace may contain checked-out source repositories, resolved baseline repositories, dependency stores, generated configuration, build outputs, logs, evidence, lock files, and provider-specific working data.

A Pipeline Workspace supports isolation and repeatability by associating the selected inputs and generated outputs with a particular pipeline execution.

Within Crucible, the Pipeline Workspace contains the repositories and artefacts referenced by a Crucible Description. Crucible records resolved source revisions so that the execution can be traced to its controlled inputs.

controlled file and execution context in which a pipeline retrieves inputs, composes baselines, performs lifecycle operations, and records intermediate and final artefacts

Generalized from continuous integration, continuous delivery, build automation, and software-pipeline usage and specialized for the Crucible architecture and operational model.

A Pipeline Workspace may exist on a developer workstation, build host, continuous-integration worker, or other execution environment.

The Pipeline Workspace is not necessarily permanent. The pipeline may preserve selected records and artefacts outside the workspace after execution completes.

A Crucible pipeline creates a Pipeline Workspace, retrieves pinned image and infrastructure repositories, builds a hardened Machine Image, records compliance findings, and stores the resulting provenance and lock information before publishing the approved artefacts.