What SCM is useful and necessary on DevOps projects?
summary
Claim: all SCM concepts remain useful in DevOps, but the upfront SCM plan is dropped in favor of lightweight, as‑needed implementation. Recommendations include automating processes and pipelines, enforcing quality gates, adopting one build by separating code and configuration data, provisioning environments, and tracing dependencies for selective testing. Evidence: banks report 4 deploys per day and other teams do 8–10 deploys/day; pipelines and automated audits are built and shown to work in regulated and fast‑moving contexts.
AI-written summary · about
chapters (10)
- 0:00Start
- 6:11Agenda
- 6:33What Is Devops
- 7:22Why Should We Use Devops
- 11:17The the Goals of Devops
- 12:12What Software Configuration Management Is
- 18:40Sub Practices for Continuous Delivery
- 22:27Microservices
- 26:15Automating of Build Processes
- 47:57Why Do You Think that Scm Is Ignored by Devops Team
related talks
32mAdopting the right DevOps Tools for you and your team
26mDevSecOps and Legacy Applications
34mYou only have to change one thing to do the DevOps
30m3 Practices for Effective DevOps Adoption
15mDevOps - Future of IT
30mDevSecOps: More Than Just Pipelines
38mDevops in an Industrial Company: From Milestones to a Continuous Quality Assurance Approach
54mEffective DevOps for Organizations