Continuous dependency updates with Depfu

Introducing Depfu at the Copenhagen Ruby Brigade meet up.

https://depfu.com - https://twitter.com/depfu

Transcript

1. Continuous dependency updates with Depfu Copenhagen / 10.5.17 / CPH.rb
2. Who here is updating dependencies?
3. Who here is regularly updating dependencies?
4. Who is using a tool to help with dependency updates?
5. Why even bother updating dependencies?
6. What if there’s a security vulnerability in one of your dependencies? How do you find out? Will it be easy to deploy a fix?
7. 1. Security 2. Security 3. Security 4. Other reasons
8. Other reasons?
9. “codebase hygiene”
10. Code gets faster. Code gets better. APIs get better. Mostly.
11. Security Goal: Minimize the time it takes to roll out a security patch.
12. Updating dependencies gets harder and harder the more you are behind.
13. What’s painful now
14. Who got time for that?
15. When? Who?
16. Part of your dev process?
17. “Never change a running system”
18. Information gathering (changelogs)
19. Upgrading dependencies is a pretty boring and thankless job. Let Depfu help you
20. Pull Request > Email (Not yet another inbox)
21. Make informed decisions - what changed? - successful build?
22. Pain is better in small doses
23. A continuous process for your team
24. How Depfu works
28. 1. We: Update Gemfile / Gemfile.lock 2. We: Create topic branch (depfu/update-rake-11.0.2) 3. CI runs your test 4. We: Create pull request with detailed info 5. You: Click that merge button. Done.
31. Give it a try. Tell us what’s good. Tell us what’s bad.
32. Support us to build a tool that really helps you
33. https://depfu.io hi@depfu.io @depfu