Automate or Stagnate: Surviving the Era of Continuous Updates
summary
The talk presents the problem of neglected open‑source dependencies and malicious packages in modern apps, citing that most apps use OSS while many dependencies stay unupdated and registries host hundreds of thousands of malicious packages. The concrete solution is to adopt Updatecli: declare sources, targets and conditions, integrate with GitOps (GitHub/GitLab Actions), generate manifests via templating and open automated PRs; a Docker Compose/Helm chart repo example reduced release time from ~1.5 weeks to under a day.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:13Software dependency complexity
- 5:00Dependency update strategies
- 8:15Alfresco case study
- 13:50Automate updates with Update CLI
- 15:59How Update CLI works
- 20:39Update CLI pros and cons
- 23:50Practical config example
- 27:02Update CLI community and future
- 28:07Q&A
related talks
29mDependency Management: Where the Fork are We?
05mContinuously Update Everything
32mAdapting DevOps in a World of Growing Software Supply Chain Attacks
35mThe Dawn of Liquid Software
31mIndustrialize Maintenance of Your Dev and Ops Stacks
48mDevOps Patterns and Antipatterns for Continuous Software Updates
30mDevOps Patterns and Antipatterns for Continuous Software Updates
27mDevOps Patterns and Antipatterns for Continuous Software Updates