public:99_annexes:annex-b-terms-and-definitions:p:pipeline_workspace

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:p:pipeline_workspace [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:p:pipeline_workspace [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Pipeline Workspace ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +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 artifacts.
 +
 +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 artifacts referenced by a [[public:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]]. Crucible records resolved source revisions so that the execution can be traced to its controlled inputs.
 +
 +===== Definition =====
 +
 +//controlled file and execution context in which a pipeline retrieves inputs, composes baselines, performs lifecycle operations, and records intermediate and final artifacts//
 +
 +===== Source =====
 +
 +Generalized from continuous integration, continuous delivery, build automation, and software-pipeline usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +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 artifacts outside the workspace after execution completes.
 +
 +===== Example =====
 +
 +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 artifacts.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>