Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Release This! Tools for a Smooth Release Cycle

3,394 views

Published on

An overview of the improved Guerrilla Games release process and the tools to support it.

  • Sex in your area is here: ❶❶❶ http://bit.ly/2Qu6Caa ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Follow the link, new dating source: ❤❤❤ http://bit.ly/2Qu6Caa ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Release This! Tools for a Smooth Release Cycle

  1. 1. Release This! Tools for a smooth release cycle Frank Compagner. Lead Tools Programmer. Guerrilla Games – Sony Computer Entertainment.
  2. 2. Contents <ul><li>Problem background </li></ul><ul><li>Stumbling though a release cycle </li></ul><ul><li>An improved process </li></ul><ul><li>A steady crawl with the occasional scramble </li></ul><ul><li>Release Tools </li></ul><ul><li>Tools for the marathon of a full release cycle </li></ul><ul><li>Conclusion </li></ul><ul><li>Limitations and extensions </li></ul>
  3. 3. Problem background Stumbling though a release cycle
  4. 4. Project overview Duration 2.5 years Developers: 120 local 80 remote QA staff 10 local 60 remote Head revision 350 GB 700.000 files Change / week 15 GB Depot size 2 TB
  5. 5. The old approach <ul><li>Create a release branch a month before each deliverable. </li></ul><ul><li>Test and fix (mostly) on the branch </li></ul><ul><li>Release whenever branch has stabilized enough </li></ul><ul><li>Hope that happens before the deadline </li></ul>main release change release
  6. 6. The old problems <ul><li>Large head revision makes branch switching painful </li></ul><ul><li>Hard to test changes break the release build </li></ul><ul><li>No control over what goes on the branch when </li></ul><ul><li>Hard to find out which changes made it into which build </li></ul><ul><li>Panic and chaos surround each release </li></ul>main release change release
  7. 7. An improved process A steady crawl with the occasional scramble
  8. 8. Improved process <ul><li>Work on main, test on release </li></ul><ul><li>Only a few selected fixes integrated to stabilize release </li></ul><ul><li>Intermediate release at end of week </li></ul><ul><li>Full copy up at start of next week </li></ul><ul><li>Final cycle takes 2-3 weeks </li></ul>main release
  9. 9. Better, but... Only sustainable for a couple of weeks
  10. 10. Release Tools Tools for the marathon of a full release cycle
  11. 11. Tools change everything <ul><li>Improve visibility of changes on release branch </li></ul><ul><li>Make it easy to see which change is in which build </li></ul><ul><li>User to request integration to release branch </li></ul><ul><li>Allow classification and review of changes </li></ul><ul><li>Facilitate integration by build team </li></ul><ul><li>All relevant information in one place </li></ul><ul><li>Full dependency information </li></ul>
  12. 12. Release Manager – User Changes
  13. 13. Release Manager – Change Details
  14. 14. Release Manager – Pending Changes main release
  15. 15. Release Manager – Released Changes
  16. 16. Release Manager - Implementation <ul><li>1500 lines of Python, using CherryPy, P4Python and jQueryUI </li></ul><ul><li>Integrates with CruiseControl, DevTrack and P4Web </li></ul><ul><li>First version done in two weeks (followed by lots of tweaking) </li></ul><ul><li>Manages change relations through changelist comments </li></ul>
  17. 17. Release Tool – Does the real work Description : Integrate //depot/KZ3/...@1237004 to //depot/KZ3-Release/... Original message: Change 1237004 by alex@busby7 On Sun 19-Dec-2010 13:30 Fix for bug 21962. Reset the fade out delay on clean up.
  18. 18. Conclusion Limitations and extensions
  19. 19. Limitations and extensions <ul><li>Requires in-depth knowledge at the build team </li></ul><ul><li>Large feature development on main cause conflicts </li></ul><ul><li>Constant effort needed to control divergence </li></ul><ul><li>Would benefit from proper jobs / bug integration </li></ul><ul><li>Dependency information can be extended </li></ul><ul><li>User groups, search functionality needed </li></ul><ul><li>Performance becomes a concern at > 10.000 changes </li></ul>
  20. 20. How I learned to stop worrying and embrace the merge-up
  21. 21. Questions?

×