The bugfix confirmation loop - PyConFI 2013

378 views

Published on

Slides for my talk at PyConFI 2013

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
378
On SlideShare
0
From Embeds
0
Number of Embeds
75
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The bugfix confirmation loop - PyConFI 2013

  1. 1. The bugfix confirmation loop Niklas Närhinen / @nnarhinen
  2. 2. @nnarhinen • Web developer • Open source developer (trying..) • part-time freelancer
  3. 3. Flowplayer
  4. 4. Flowplayer • Flowplayer Flash
  5. 5. Flowplayer • Flowplayer Flash • Flowplayer HTML5
  6. 6. Flowplayer • Flowplayer Flash • Flowplayer HTML5 • More to come..
  7. 7. Flowplayer HTML5 • HTML5 <video> tag • CSS3 • Encodings • HTTP servers • Browsers..
  8. 8. Automated test suite • There is none :( • Planned to near future
  9. 9. Bug reports • Often reproducable on only one • ..browser • ..jQuery version • ..video • ..computer
  10. 10. Fix • Reproducable demo • Code code code code • ??? • Profit!
  11. 11. Problem with Flowplayer issues • Fix verification • Idea: Ship fixed build to customer • yeah, not going to happen
  12. 12. Better • Build the complete demo site with the new player
  13. 13. Gitbot • Continuous deployment tool • Configuration with Python and Yaml ➡ Super flexible • Project build dependency - Cool!
  14. 14. Gitbot • http://gitbot.io/ • https://github.com/gitbot • In a developing phase - documentation will follow
  15. 15. 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
  16. 16. Pull requests • Every pull request will get built
  17. 17. Pull requests Pull request version Development branch Latest stable
  18. 18. What actually happens
  19. 19. What actually happens • Gitbot fetches sources for flowplayer
  20. 20. What actually happens • Gitbot fetches sources for flowplayer • It builds the player
  21. 21. 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/)
  22. 22. 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
  23. 23. Conclusion
  24. 24. Conclusion • Automating builds is beneficial
  25. 25. Conclusion • Automating builds is beneficial • Choose the right workflow for your product / team
  26. 26. Conclusion • Automating builds is beneficial • Choose the right workflow for your product / team • Publish visible results
  27. 27. Thank you! • Questions, feedback? ➡@nnarhinen

×