A Target Environment is the environment selected to receive, execute, host, verify, or operate a build artifact, software release, machine image, infrastructure baseline, or deployment.
The Target Environment establishes the applicable technical, security, compliance, connectivity, capacity, and operational constraints for the deployment.
A Target Environment may be a development, test, staging, production, recovery, cloud, on-premises, disconnected, or air-gapped environment.
The Target Environment influences image selection, infrastructure configuration, dependency availability, compliance requirements, provider capabilities, and deployment procedures.
environment selected to receive, execute, host, verify, or operate a build artifact, software release, machine image, infrastructure baseline, or deployment
Generalized from systems engineering, software delivery, deployment, and operational-environment usage and specialized for the Crucible architecture and operational model.
A Target Environment identifies the destination of a defined build or deployment activity. The same environment may serve as the Target Environment for one activity and as a source or build environment for another activity.
A Target Environment may contain one or more Execution Environments.
A deployment description identifies an air-gapped enclave as the Target Environment for a hardened Kubernetes platform. Crucible selects the required machine images, infrastructure definitions, dependencies, and transfer process for that environment.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.