Workspace

Go up to Terms and Definitions

A Workspace provides an identified working area in which a person, automated process, or Workflow accesses and processes selected revisions of managed content.

A Workspace can contain:

• Checked-out repository content
• Selected Revisions
• Image Layers
• Infrastructure Baselines
• Application source
• Declarative Configuration
• Build inputs
• Generated Artifacts
• Intermediate results
• Execution logs
• Validation results

A Workspace can exist on a developer system, within an automated execution environment, or as part of a CI/CD Pipeline.

Within Crucible documentation, a Workspace provides the bounded working context in which Crucible consumes selected repositories, performs Baseline Composition, processes deployment-related steps, and produces identifiable results.

identified working area containing selected managed content and execution inputs used by a person or automated process to perform one or more operations

DIDO-controlled term adapted from established version-control, software-build, development-environment, and CI/CD practices.

A Workspace is a working context rather than the authoritative source of the managed content it contains.

Content in a Workspace can derive from one or more repositories and identified Revisions.

A Workspace differs from a repository. A repository records and manages revisions of content, while a Workspace contains selected content used for an identified execution or activity.

A Workspace differs from an Execution Environment. The Workspace contains the selected working content and inputs; the Execution Environment supplies the resources and conditions under which operations execute.

A Workspace can be temporary or persistent.

A CI/CD Pipeline creates a Workspace, checks out identified revisions of an Image Layer repository and an Infrastructure Baseline repository, adds optional application source, and invokes Crucible to perform Baseline Composition and deployment-related operations.