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:b:build_dependency [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public: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: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Build Dependency is a [[public: | ||
| + | |||
| + | A Build Dependency may include source material, installation media, software packages, libraries, build tools, provisioning content, compliance content, credentials, | ||
| + | |||
| + | 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: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from software engineering, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Build Dependency differs from a [[public: | ||
| + | |||
| + | 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, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||