Build Operation [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Build Operation ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Build Operation transforms identified inputs according to an identified set of build instructions and produces one or more output [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] or a recorded failure result.

Build inputs can include:

  * Source content
  * An identified [[dido:99_annexes:annex-b-terms-and-definitions:g:git|Git]] repository state
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration|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 [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]] or [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]].

===== Definition =====

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

===== Source =====

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

===== Note =====

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.

===== Example =====

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.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>