Downloaded 14 times
Uploaded byRobert Reiz
Continuous Updating with VersionEye at code.talks 2014
Robert Reiz, a software developer since 1998, discusses the importance of continuous updating in dependency management, emphasizing that outdated libraries can pose significant risks. He highlights the shift from the waterfall model to agile development and the need for tools like VersionEye to automate tracking and managing dependencies effectively. The document also covers semantic versioning and the necessity of migration paths to ensure system stability during updates.
More Related Content
Similar to Continuous Updating with VersionEye at code.talks 2014
Continuous Updating with VersionEye at code.talks 2014
- 1.
- 2. Who I am? • Robert Reiz • Software Dev since 1998 • I started VersionEye
- 3. What I do? • I write crawlers • I integrate Package Managers • I integrate SCMs
- 4. VersionEye Dependency Management • 445K Open Source Projects • 10 Package Managers • 3 SCMs
- 5.
- 6.
- 7. Why I wantto stay up-to-date?
- 8. 100 libraries per project in avg.
- 9. How do youkeep track of your Dependencies?
- 10. Which Licenses are your dependencies using?
- 11. Are your dependencies still alive?
- 12.
- 13. Every dependency isa risk factor.
- 14. 15 years agowe used to work with the WATERFALL MODEL Requirements Analysis Design Coding Testing Accepting
- 15. But today weare AGILE
- 16. Everything the WaterfallModel used to execute in one year ... ! ... we nowadays execute in 2 weeks!
- 17. The way wedevelop software today totally changed!
- 18. Being AGILE gotus CONTINUOUS Testing CONTINUOUS Refactoring CONTINUOUS Integration CONTINUOUS Delivery CONTINUOUS Deployment
- 19. But what about Continuous Updating?
- 20. Why should Icare about Continuous Updating?
- 21. Core committers don’trelease new versions just for fun!
- 22. They always havegood reasons • Bug Fixes • Security Fixes • Speed & Memory optimization • New Features
- 23. If you can'tfly then run, if you can't run then walk, if you can't walk then crawl, but whatever you do you have to keep moving forward. Martin Luther King Jr.
- 24. How do youensure that new versions don’t break the system?
- 25. Semantic Versioning MigrationPaths Continuous Testing
- 26.
- 27. MAJOR.MINOR.PATCH 1.MAJOR versionwhen you make incompatible API changes 2.MINOR version when you add functionality in a backwards-compatible manner 3.PATCH version when you make backwards-compatible bug fixes.
- 28. Always follow the MIGRATION PATH
- 29. Many small stepsare better than one big step ! You can do SMALL MIGRATIONS on the fly. ! BIG MIGRATIONS are risky and expensive. ! If you miss versions, you miss migration paths, too. And that leads to TROUBLE!
- 30. Don’t miss migrationpaths! migrate migrate migrate 1 2 3 4 big migration … expensive!
- 31. Always run yourTESTS against new versions
- 32.
- 33. New$Releases$ Major# Minor/Patch# 6%# 94%#
- 34. 94% of allnew releases are harmless and you can update without doubt.
- 35. Another reason forbeing current
- 36. Do you reallybelieve those young talents wanna work with COBOL? Or other OLD SHIT?
- 37. Tracking versions isa pain!
- 38. SOFTWARE LIBRARIES areNOT like iPhone Apps!
- 39. 100 libraries per project in avg. After 2 weeks the first libraries are OUT-DATED!
- 40. Developers are missingcritical BUG FIXES and important UPDATES!
- 41. Manually checking for updates is no fun! ! It cost TIME & MONEY! ! NOBODY WANTS TO DO IT!
- 42. So, how doyou wanna solve this PROBLEM
- 43. You have to AUTOMATE
- 44. You need aTOOL for that!
- 45. GemNotifier Gemnasium VersionEye Languages Ruby Ruby, Node.JS, Python 22 Languages GitHub no yes yes Bitbucket no no yes File upload no no yes URL parsing no no yes Changelogs no yes in progress Security no yes in progress Licenses no no yes API no no yes
- 46. www.VersionEye.com Keeps aneye on more than 445K open source libraries! Supports 22 Languages and 10 Package Managers! Integrated with GitHub, Bitbucket, Stash. Open REST JSON API.
- 47. Are your dependencies still alive?
- 48.
- 49. Heat-map for dead/ alive Dependencies
- 50.
- 51. Which Licenses are your dependencies using?
- 52.
- 53.
- 54.
- 55. M2 VersionEye Enterprise VM VersionEye.com CI Intranet E-Mail data sync SCM VersionEye Enterprise Updates via Docker Containers
- 56.