Version-Controlled Artifact

Go to Terms and Definitions

A Version-Controlled Artifact is an Artifact managed through a Version Control System.

The Version Control system assigns a unique revision to the Artifact and allows an authorized user or process to retrieve it.

A Version-Controlled Artifact may include:

• Source code
• Configuration files
• Infrastructure Configurations
• Infrastructure Blueprints
• Schemas
• Models
• Scripts
• Policy files
• Documentation
• Build specifications

Placing an Artifact under Version Control distinguishes identifiable revisions of the Artifact from uncontrolled copies or informal working material.

A Version-Controlled Artifact differs from a revision history:

• The Version-Controlled Artifact is the controlled Artifact
• The revision identifies a particular state of the Artifact
• The revision history records the succession of revisions associated with the Artifact

artifact managed by a version control system that assigns identifiable revisions and permits retrieval of an identified revision

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

A Version-Controlled Artifact does not necessarily have an approved, released, or deployed status.

Version Control establishes revision identification and retrieval. Separate requirements may govern:

• Revision preservation
• Change review
• Change approval
• Release designation
• Deployment authorization
• Retention
• Retirement

The term does not require a particular Version Control product, repository implementation, branching model, or storage technology.

A machine-readable Infrastructure Configuration stored in a Version Control repository with an identifiable revision that an authorized pipeline can retrieve is a Version-Controlled Artifact.