The bugfix confirmation loop - PyConFI 2013
0 likes457 views
The document discusses using Gitbot, a continuous deployment tool, to automate building and testing Flowplayer, a video player library. Gitbot fetches the Flowplayer code and demo site code from GitHub, builds them, publishes the demo site to S3, and updates DNS records on every code push or pull request. This allows Flowplayer developers to more easily reproduce, fix, and verify bugs without having to manually deploy to different environments. Automating builds in this way helps improve quality and catch bugs earlier.
The bugfix confirmation loop - PyConFI 2013
- 1. The bugfix confirmation loop Niklas Närhinen / @nnarhinen
- 3. @nnarhinen • Web developer • Open source developer (trying..) • part-time freelancer
- 4. Flowplayer
- 6. Flowplayer • Flowplayer Flash • Flowplayer HTML5
- 7. Flowplayer • Flowplayer Flash • Flowplayer HTML5 • More to come..
- 8. Flowplayer HTML5 • HTML5 <video> tag • CSS3 • Encodings • HTTP servers • Browsers..
- 9. Automated test suite • There is none :( • Planned to near future
- 10. Bug reports • Often reproducable on only one • ..browser • ..jQuery version • ..video • ..computer
- 11. Fix • Reproducable demo • Code code code code • ??? • Profit!
- 12. Problem with Flowplayer issues • Fix verification • Idea: Ship fixed build to customer • yeah, not going to happen
- 13. Better • Build the complete demo site with the new player
- 14. Gitbot • Continuous deployment tool • Configuration with Python and Yaml ➡ Super flexible • Project build dependency - Cool!
- 15. Gitbot • http://gitbot.io/ • https://github.com/gitbot • In a developing phase - documentation will follow
- 16. Gitbot - workflow • At flowplayer • • master - stable • http://demos.flowplayer.org/ dev - next release version • • http://demos.dev94.flowplayer.us/ Built on every push to dev
- 17. Pull requests • Every pull request will get built
- 21. Pull requests Pull request version Development branch Latest stable
- 23. What actually happens • Gitbot fetches sources for flowplayer
- 24. What actually happens • Gitbot fetches sources for flowplayer • It builds the player
- 25. What actually happens • Gitbot fetches sources for flowplayer • It builds the player • Gitbot fetches sources for the demo site • (Hyde, http://ringce.com/hyde, http:// hyde.github.io/)
- 26. What actually happens • Gitbot fetches sources for flowplayer • It builds the player • Gitbot fetches sources for the demo site • (Hyde, http://ringce.com/hyde, http:// hyde.github.io/) • Publishes built site to S3, updates DNS
- 27. Conclusion
- 28. Conclusion • Automating builds is beneficial
- 29. Conclusion • Automating builds is beneficial • Choose the right workflow for your product / team
- 30. Conclusion • Automating builds is beneficial • Choose the right workflow for your product / team • Publish visible results
- 31. Thank you! • Questions, feedback? ➡@nnarhinen