dido: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

dido:99_annexes:annex-b-terms-and-definitions:p:pipeline_workspace [2026/07/13 11:34] – created nick_didodido:99_annexes:annex-b-terms-and-definitions:p:pipeline_workspace [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ===== Discussion ===== ===== 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 artefacts.+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. 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.
Line 11: Line 11:
 A Pipeline Workspace supports isolation and repeatability by associating the selected inputs and generated outputs with a particular pipeline execution. 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 [[dido: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.+Within Crucible, the Pipeline Workspace contains the repositories and artifacts referenced by a [[dido: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 ===== ===== Definition =====
  
-//controlled file and execution context in which a pipeline retrieves inputs, composes baselines, performs lifecycle operations, and records intermediate and final artefacts//+//controlled file and execution context in which a pipeline retrieves inputs, composes baselines, performs lifecycle operations, and records intermediate and final artifacts//
  
 ===== Source ===== ===== Source =====
Line 25: Line 25:
 A Pipeline Workspace may exist on a developer workstation, build host, continuous-integration worker, or other execution environment. 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.+The Pipeline Workspace is not necessarily permanent. The pipeline may preserve selected records and artifacts outside the workspace after execution completes.
  
 ===== Example ===== ===== 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 artefacts.+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.
  
 ---- ----
  • dido/99_annexes/annex-b-terms-and-definitions/p/pipeline_workspace.1783967665.txt.gz
  • Last modified: 2026/07/13 11:34
  • by nick_dido