FR-DSO-004 — Automated Build Execution

Go to C.3.8 DevSecOps Integration

Statement

Crucible SHALL execute automated Build Operations.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DSO-004The Original Requirement states:

The system shall support automated build execution.[C1]

FR-DSO-004:

Replaces The system with the defined system name CrucibleChanges shall to the established uppercase normative form SHALLReplaces the weak phrase support automated build execution with the direct and observable behavior execute automated build operationsNo other substantive normalization is required.

Rationale

An automated build operation transforms identified source content, configuration, dependencies, or other inputs into one or more output Artifacts without requiring interactive execution by an operator.

Automated build execution enables repeatable build behavior within Development, Security, and Operations (DevSecOps) Workflows and CI/CD Pipelines.

A build operation can use:

Source filesGit repository statesBuild instructionsDeclarative ConfigurationDependenciesBuild parametersBuild toolsBuild environmentsA build operation can produce:

Executable softwareLibrariesPackagesContainer ImagesMachine ImagesConfiguration ArtifactsDeployment ArtifactsBuild logsBuild metadataBuild statusThis requirement establishes automated build execution without prescribing:

A particular build toolA particular programming languageA particular source repositoryA particular build environmentA particular output Artifact typeA particular dependency-resolution mechanismA particular CI/CD PipelineBuild validationArtifact signingArtifact publicationDeployment of the resulting ArtifactsSeparate requirements, architecture specifications, build definitions, and Workflow definitions govern those subjects and behaviors.

Applies To

This requirement applies to:

Automated build operationsBuild inputsBuild output ArtifactsDevSecOps WorkflowsCI/CD Pipelines

Verification

Verification confirms that:

A build definition and its required inputs are selected for testingCrucible initiates the build operation without interactive operator executionCrucible executes the selected build operationThe build operation completes with an observable statusThe resulting build output or failure information can be identified

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Issues

Notes for Editors

This requirement page retains the stable requirement identifier FR-DSO-004.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement addresses execution of automated build operations.

FR-DSO-001 governs integration with Git-based Workflows.

FR-DSO-002 governs integration with GitOps Workflows.

FR-DSO-003 governs integration with CI/CD Pipelines.

FR-DSO-005 governs automated deployment execution.

FR-DSO-006 governs automated validation execution.

Do not add particular build tools, programming languages, repositories, build environments, dependency mechanisms, output Artifact types, signing operations, publication operations, or deployment obligations unless the controlling requirement changes through an approved requirements process.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:fr-dso-004#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.