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_dependency [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:b:build_dependency [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Build Dependency ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Build Dependency is a [[public:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependency]] required to produce, assess, package, sign, or otherwise prepare a build artifact.
 +
 +A Build Dependency may include source material, installation media, software packages, libraries, build tools, provisioning content, compliance content, credentials, repositories, provider plugins, or supporting services.
 +
 +A Build Dependency is required during the build process but may not be required when the resulting artifact operates in its target environment.
 +
 +Within Crucible, Build Dependencies may be retrieved, pinned, captured, recorded, and transferred so that an [[public:99_annexes:annex-b-terms-and-definitions:i:image_build|Image Build]] can be reproduced in a connected or disconnected environment.
 +
 +===== Definition =====
 +
 +//[[public:99_annexes:annex-b-terms-and-definitions:d:dependency|dependency]] required to produce, assess, package, sign, or otherwise prepare a build artifact//
 +
 +===== Source =====
 +
 +Generalized from software engineering, machine-image engineering, dependency management, and reproducible-build usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Build Dependency differs from a [[public:99_annexes:annex-b-terms-and-definitions:r:runtime_dependency|Runtime Dependency]]. A Build Dependency supports creation or preparation of an artifact, while a Runtime Dependency supports operation of the resulting system, service, or workload.
 +
 +The same Dependency may act as both a Build Dependency and a Runtime Dependency in different lifecycle contexts.
 +
 +===== Example =====
 +
 +An Image Build depends on installation media, package repositories, Packer, Ansible collections, and compliance content. These inputs are Build Dependencies because the build process requires them to produce and assess the Machine Image.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>