public:99_annexes:annex-b-terms-and-definitions:b:build_pipeline

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:b:build_pipeline [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:b:build_pipeline [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Build Pipeline ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Build Pipeline is an automated sequence of controlled activities that transforms defined inputs into one or more build artifacts and associated records.
 +
 +The pipeline may retrieve source material, resolve dependencies, compile or assemble software, create [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]], apply configuration, perform testing, execute compliance assessments, generate evidence, sign artifacts, and publish results.
 +
 +A Build Pipeline coordinates its activities through defined inputs, outputs, dependencies, transition conditions, error handling, and execution controls.
 +
 +Within Crucible, a Build Pipeline may use a [[public:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] to orchestrate source retrieval, [[public:99_annexes:annex-b-terms-and-definitions:i:image_build|Image Build]], compliance assessment, image upload, and preparation for [[public:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]].
 +
 +===== Definition =====
 +
 +//automated sequence of controlled activities that transforms defined inputs into one or more build artifacts and associated records//
 +
 +===== Source =====
 +
 +Generalized from software engineering, continuous integration, continuous delivery, build automation, and configuration-management usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Build Pipeline may contain both build activities and supporting activities such as validation, scanning, signing, evidence generation, and publication.
 +
 +A Build Pipeline differs from a single build command because it coordinates multiple controlled activities and preserves the relationships among their inputs and outputs.
 +
 +===== Example =====
 +
 +A Crucible Build Pipeline retrieves pinned image and infrastructure repositories, builds a hardened [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 image, runs a [[public:99_annexes:annex-b-terms-and-definitions:s:stig|Security Technical Implementation Guide (STIG)]] assessment, records provenance, signs the resulting image, and publishes its Image Record.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>