public:99_annexes:annex-b-terms-and-definitions:v:version_pinning

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:v:version_pinning [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:v:version_pinning [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Version Pinning ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Version Pinning selects and records an exact version or revision of an input for use by a defined build, deployment, assessment, or operational process.
 +
 +The selected value may identify a source revision, software package version, container image digest, machine-image identifier, compliance benchmark release, tool version, plugin version, or other controlled input.
 +
 +Version Pinning prevents an execution from silently selecting a later or otherwise different input when the original input remains required.
 +
 +Within Crucible, Version Pinning supports [[public:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], and [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] by connecting each result to the exact revisions used to produce it.
 +
 +===== Definition =====
 +
 +//selection and recording of an exact version or revision of an input for use by a defined process//
 +
 +===== Source =====
 +
 +Generalized from software configuration management, dependency management, package management, and reproducible-build usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A symbolic label, branch name, or unqualified latest-version reference does not provide reliable Version Pinning when the referenced content can change without changing the reference.
 +
 +Version Pinning identifies the selected input. It does not by itself verify the integrity, authenticity, compatibility, or suitability of that input.
 +
 +===== Example =====
 +
 +A Crucible Description identifies a repository tag, and the pull process resolves the tag to an exact Git commit. The recorded commit identifier pins the repository content used by the build.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>