| Both sides previous revision Previous revision | |
| public:99_annexes:annex-b-terms-and-definitions:b:build_pipeline [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:b:build_pipeline to public:99_annexes:annex-b-terms-and-definitions:b:build_pipeline nick_dido | public: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 |
|---|
| ====== Build Pipeline ====== | ====== Build Pipeline ====== |
| |
| [[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| A Build Pipeline is an automated sequence of controlled activities that transforms defined inputs into one or more build artifacts and associated records. | 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 [[private: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. | 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. | 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 [[private:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] to orchestrate source retrieval, [[private:99_annexes:annex-b-terms-and-definitions:i:image_build|Image Build]], compliance assessment, image upload, and preparation for [[private:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]]. | 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 ===== | ===== Definition ===== |
| ===== Example ===== | ===== Example ===== |
| |
| A Crucible Build Pipeline retrieves pinned image and infrastructure repositories, builds a hardened [[private:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 image, runs a [[private: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. | 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. |
| |
| ---- | ---- |