Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:i:image_build [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:i:image_build [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Image Build ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Image Build is a controlled process that transforms defined inputs into a [[public: | ||
| + | |||
| + | The process may retrieve installation media, create storage structures, install an operating system, apply provisioning content, configure services, add packages, perform security hardening, run compliance scans, and record the resulting artifacts and [[public: | ||
| + | |||
| + | An Image Build uses an [[public: | ||
| + | |||
| + | Within Crucible, an Image Build may produce a [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from machine-image engineering, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Image Build identifies the complete controlled process rather than only the execution of a particular build tool. | ||
| + | |||
| + | Repeated Image Builds from the same controlled inputs should produce results that satisfy the applicable reproducibility criteria, even when generated identifiers or environment-specific metadata differ. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Crucible Image Build boots the [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||