Increased Responsiveness Establishing Interoperability Between Development and Operations Teams
Version Control Tool Rapid Delivery Aligning Software Goals across Development and Operations Teams Development Tool DevOps Benefits Responsive Scalability Increasing the Frequency of Software Releases Source Code Management Repository Increased Reliability Increasing the Speed and Quality of Software Releases Configuration Management Database (CMDB) Improved Security Improving Software Quality in Response to Feedback Configuration Approval Tool DevOps Goals Decreasing Lead Times Issue Tracking System Build Server Conflicting Culture Artifact Repository Development Firmly Isolated Dev and Ops Deployment Tool Operations DevOps Primary Roles Establishing Unified Metrics QA DevOps Challenges Operations Tool Overlooking Security and Governance Requirements Release Management Tool Too Much Focus on Tools Policy System Legacy Infrastructure Limitations Monitoring Agents Undesirable DevOps Department DevOps Tools, Systems & Feedback Tool Unacceptable Rate of Adoption Repositories CI Server Continuous Integration (CI) Deployment Server Key DevOps Practices Continuous Delivery (CD) Packaging Tool DevOps Module 1 Continuous Deployment Continuous Integration (CI) Fundamental DevOps Culture Reporting Tool Continuous Monitoring Collaboration Communication and Collaboration Tool DevOps Impacts Infrastructure-as-Code (IaC) Automation Configuration-as-Code (CaC) Submit/Build/Test Measurement principles Policy-as-Code (PaC) Use a Central Code Repository Develop Submit Code Frequently best practices CI/CD Delivery Pipeline Build Create More Builds Continuous Delivery (CD) Plan Integrate Automate Build Creation Create principles DevOps Lifecycle Stages Test Automate Deployment Verify Repeatable Reliable Process Release Test in Staging Package Automate Everything Deploy Test Before Submit Continuous Deployment Release Version Control and Source Control Everything Operate Do Not Submit on Broken Code Configure Prioritize Challenging Tasks Automated Release Verification Perform Proper Testing Monitor Built-in Quality Dependency Management Share Test Results Feedback Build Binaries Only Once Done Means Released Infrastructure Resource Staging Use Same Deployment Tool and Method Shared Responsibility of Release Process Infrastructure Resource Compliance Verification Across Environments Continuous Improvement Carry Out a “Smoke Test” Deployment ® ®