public:99_annexes:annex-b-terms-and-definitions:d:devops

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:d:devops [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:devops [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Development and Operations (DevOps) ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Development and Operations (DevOps) integrates software-development and operational activities into a coordinated lifecycle.
 +
 +DevOps reduces organizational and procedural separation between the people, processes, and technologies that develop, build, test, release, deploy, operate, and maintain software and systems.
 +
 +DevOps commonly uses:
 +
 +  * Shared repositories
 +  * Automated build processes
 +  * Automated testing
 +  * Continuous Integration
 +  * Continuous Delivery
 +  * Continuous Deployment
 +  * Configuration management
 +  * Infrastructure as Code
 +  * Git-based workflows
 +  * GitOps practices
 +  * Automated deployment
 +  * Operational monitoring
 +  * Rapid feedback
 +  * Repeatable workflows
 +
 +Within Crucible documentation, DevOps provides the broader lifecycle context for integrating repository changes, automated builds, deployments, validation activities, and operational feedback.
 +
 +DevOps does not by itself establish the security practices required throughout that lifecycle. [[public:99_annexes:annex-b-terms-and-definitions:d:devsecops|Development, Security, and Operations (DevSecOps)]] explicitly integrates security into DevOps activities.
 +
 +===== Definition =====
 +
 +//coordinated approach that integrates software-development and operational activities, processes, and responsibilities throughout the software or system lifecycle//
 +
 +===== Source =====
 +
 +Adapted from:
 +
 +  * National Institute of Standards and Technology Special Publication 800-204A
 +  * National Institute of Standards and Technology Special Publication 800-218
 +  * National Institute of Standards and Technology Cybersecurity Practice Guide 1800-44
 +
 +===== Note =====
 +
 +The term **DevOps** combines **Development** and **Operations**.
 +
 +DevOps is an organizational and engineering approach rather than a particular tool, product, deployment platform, or CI/CD implementation.
 +
 +Automation commonly enables DevOps practices, but automation alone does not establish DevOps. DevOps also requires coordination between development and operations and feedback across lifecycle activities.
 +
 +DevOps differs from [[public:99_annexes:annex-b-terms-and-definitions:d:devsecops|Development, Security, and Operations (DevSecOps)]]. DevSecOps integrates security practices and responsibilities throughout the DevOps lifecycle.
 +
 +===== Example =====
 +
 +A development team commits a configuration change to a Git repository. An automated pipeline builds the affected Artifact, performs tests, deploys it to a target environment, validates the deployment, and provides the resulting status to development and operations personnel.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>