Build Operation

Go up to Terms and Definitions

A Build Operation transforms identified inputs according to an identified set of build instructions and produces one or more output Artifacts or a recorded failure result.

Build inputs can include:

• Source content
• An identified Git repository state
• Declarative Configuration
• Dependencies
• Build parameters
• Build instructions
• Tool definitions
• Environment definitions

Build outputs can include:

• Executable software
• Libraries
• Packages
• Container Images
• Machine Images
• Configuration Artifacts
• Deployment Artifacts
• Build metadata
• Build logs
• Build status

A Build Operation identifies the inputs, instructions, execution result, and resulting Artifacts sufficiently to distinguish one build execution from another.

Within Crucible documentation, a Build Operation can execute manually or as part of an automated Workflow or CI/CD Pipeline.

operation that transforms identified inputs according to identified build instructions and produces one or more output Artifacts or a recorded failure result

DIDO-controlled term adapted from established software build, configuration-management, and CI/CD practices.

A Build Operation is an execution, not merely a build definition.

A build definition specifies how a Build Operation is performed. A Build Operation applies that definition to identified inputs.

A Build Operation does not necessarily compile source code. It can assemble, package, transform, generate, or otherwise produce an Artifact.

A successful Build Operation produces the required output Artifacts. An unsuccessful Build Operation produces an identifiable failure result.

Crucible executes a Build Operation using an identified Git commit, build instructions, dependency set, and build environment. The operation produces a Container Image, build metadata, and an observable completion status.