This is an old revision of the document!
C.3.8 DevSecOps Integration
Go to Crucible Functional Requirements
The DevSecOps Integration requirements define how Crucible participates in Git-based workflows, applies GitOps practices, operates as part of a CI/CD Pipeline, and performs automated build, deployment, and validation activities.
Together, these requirements establish noninteractive and automated workflow behavior that contributes to controlled change, repeatable execution, Reproducibility, Provenance, and Traceability.
Contents
Notes for Editors
The individual requirement pages should retain the stable identifiers FR-DSO-001 through FR-DSO-006.
Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.
The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.
Normalized Statements should use direct, testable behavior and should identify the applicable repository state, workflow event, CI/CD Pipeline operation, input Artifact, and required result.
Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.
Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.
To reference a requirement Statement from another wiki page, insert:
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
Replace <namespace> with the namespace of the requirement leaf page.
The section name following # SHALL match the section heading verbatim on the requirement page.
Do not rename a requirement page after an external citation unless a redirect or move plan is in place.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.