====== FR-DSO-003 — CI/CD Pipeline Integration ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|Go to C.3.8 DevSecOps Integration]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL integrate with [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]].

===== Derived From =====

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DSO-003

The Original Requirement states:

> //The system shall integrate with CI/CD pipelines.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-DSO-003:

  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Changes **shall** to the established uppercase normative form **SHALL**
  * Links [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] to its controlling definition
  * Retains the source behavior **integrate with CI/CD pipelines**

No other substantive normalization is required.

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] coordinates automated activities that build, test, package, deliver, deploy, or validate changes.

Integration with CI/CD Pipelines enables Crucible operations to participate in automated [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflows]] initiated or coordinated by pipeline execution.

Such integration can involve:

  * Receiving pipeline inputs
  * Providing operation parameters
  * Initiating Crucible operations
  * Receiving operation status
  * Returning operation results
  * Supplying generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
  * Supplying validation results
  * Supplying [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * Reporting success or failure

This requirement establishes integration with CI/CD Pipelines without prescribing:

  * A particular CI/CD product
  * A particular pipeline provider
  * A pipeline definition format
  * A pipeline execution environment
  * A triggering mechanism
  * An integration protocol
  * An application programming interface
  * A command-line interface
  * A plugin mechanism
  * A particular build, deployment, or validation sequence

Separate requirements, architecture specifications, Workflow definitions, and interface definitions govern those subjects and behaviors.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]
  * Pipeline integration operations
  * Automated [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflows]]

===== Verification =====

Verification confirms that:

  - A [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] is selected for testing
  - The selected CI/CD Pipeline invokes or coordinates a Crucible operation
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] receives the information required to perform the selected operation
  - Crucible performs the selected operation
  - Crucible returns an observable status or result to the selected CI/CD Pipeline
  - The observed interaction demonstrates integration with the selected CI/CD Pipeline

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Implementation Status =====

Implemented and Verified

===== Requirement Status =====

<todo>Review and approve FR-DSO-003 as a leaf requirement.</todo>

----
===== Issues =====

<todo>Determine whether separate requirements identify the CI/CD Pipeline operations that Crucible must support.</todo>

<todo>Determine whether separate requirements govern pipeline authentication, authorization, and credential management.</todo>

<todo>Determine whether separate requirements define the status and result information exchanged between Crucible and a CI/CD Pipeline.</todo>

----
===== Notes for Editors =====

This requirement page retains the stable requirement identifier ''FR-DSO-003''.

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

The Statement uses the controlling Terms and Definitions entry:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]

The Statement addresses integration with CI/CD Pipelines. It does not require a particular pipeline product, provider, definition format, execution environment, triggering mechanism, protocol, interface, or plugin mechanism.

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

FR-DSO-002 governs integration with GitOps Workflows.

FR-DSO-004 through FR-DSO-006 govern automated build, deployment, and validation execution.

Do not add particular pipeline products, integration protocols, interface formats, triggering mechanisms, authentication methods, or automated execution obligations unless the controlling requirement changes through an approved requirements process.

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

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

----

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