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.

Atlassian Developers switch to DVCS - Unite London conference

737 views

Published on

Discussion of how Atlassian moved from subversion source code management to DVCS tools such as Git and Mercurial.

Covers a basic recipe for making the switch from the Atlassian experience and ideas as to why DVCS has become a competitive advantage to businesses.

Published in: Technology
  • Be the first to comment

Atlassian Developers switch to DVCS - Unite London conference

  1. 1. Distributed version control
  2. 2. build itcheck get in Task write code
  3. 3. DVCS @ Unite Issue Tracker
  4. 4. DVCS @ Unite Content Collaboration
  5. 5. Shaping the future of DVCS
  6. 6. Making the Switch to DVCSHow Atlassian teams moved from centralised todistributed version controlJohn Stevenson, UK Ambassador, Atlassian 7
  7. 7. Importance of Versioning
  8. 8. Importance of VersioningCollaboration History of changes Multiple copies
  9. 9. Importance of VersioningCollaboration History of changes Multiple copies
  10. 10. Importance of VersioningCollaboration History of changes Multiple copies
  11. 11. One repository to rule them all
  12. 12. One repository to rule them all
  13. 13. Whats the beefwith Subversion ?
  14. 14. Centralised Version Control Subversion
  15. 15. Centralised Version Control Subversion
  16. 16. Centralised Version Control Subversion
  17. 17. Subversion issues• Merging hell• Fear of breaking the build • delayed commits lead to more merging hell
  18. 18. Subversion issues• Merging hell• Fear of breaking the build • delayed commits lead to more merging hell
  19. 19. Subversion issues• Merging hell• Fear of breaking the build • delayed commits lead to more merging hell
  20. 20. Rise of DVCS • High adoption in Open Source projects • Enterprises now making the move • Atlassian teams already migrated
  21. 21. Rise of DVCS • High adoption in Open Source projects • Enterprises now making the move • Atlassian teams already migrated
  22. 22. Rise of DVCS • High adoption in Open Source projects • Enterprises now making the move • Atlassian teams already migrated
  23. 23. Everyone is doing it!
  24. 24. Everyone is doing it!
  25. 25. Social coding
  26. 26. Social coding
  27. 27. Social coding
  28. 28. Enhancing thedevelopment cycle with DVCS
  29. 29. Distributed Version Control
  30. 30. Distributed Version Control Git or Mercurial Git or Mercurial Git or Mercurial Git or Mercurial Git or Mercurial Git or Mercurial
  31. 31. DVCS encourages learning• Smaller projects• Smaller iterations / continuous deployment• Faster feedback• Greater collaboration & innovation• Understanding customers better
  32. 32. What do I need to learn
  33. 33. What do I need to learn
  34. 34. Differences in workflow?
  35. 35. Not just the command line
  36. 36. Not just the command line
  37. 37. Not just the command line The command line is like Marmite...
  38. 38. “ Distributed Version Control is flexible and can fit any ” workflow - you can even treat it like Subversion.
  39. 39. “ Distributed Version Control is flexible and can fit any ” workflow - you can even treat it like Subversion. Steve Streeting Creator of SourceTree
  40. 40. Centralised Vs Distributed
  41. 41. Classic Vs Re-imagined
  42. 42. How did Atlassian do it?Recipe for DVCSadoption
  43. 43. How did Atlassian do it?Recipe for DVCSadoption
  44. 44. Atlassian DVCS recipe
  45. 45. Atlassian DVCS recipe Tooling
  46. 46. Git and Mercurial Mac Client
  47. 47. Git and Mercurial Mac Client
  48. 48. Browse and Search source across versioning toolsCommits to SVN & DVCS reposBrowse source inSubversion, Git, Hg, CVS, etc.
  49. 49. Browse and Search source across versioning toolsCommits to SVN & DVCS reposBrowse source inSubversion, Git, Hg, CVS, etc.
  50. 50. Source code disinfectant
  51. 51. Source code disinfectant
  52. 52. Continuous Integration andrelease management• Run same builds against old and new VCS• Continuous Validation• Separate repos for integration
  53. 53. Continuous Integration andrelease management• Run same builds against old and new VCS• Continuous Validation• Separate repos for integration
  54. 54. Link every commit to JIRA issues
  55. 55. Link every commit to JIRA issues
  56. 56. Atlassian DVCS recipe
  57. 57. Atlassian DVCS recipe Practices
  58. 58. Incremental change• Try on small projects• Use hybrid tooling
  59. 59. Bringing our history with us
  60. 60. Bringing our history with us
  61. 61. Atlassian DVCS recipe
  62. 62. Atlassian DVCS recipe Experience
  63. 63. DVCS mentor
  64. 64. DVCS mentor
  65. 65. DVCS mentor
  66. 66. CodewithoutLimitations• Fork & Clone• Repositories are cheap, dont be afraid to mess up
  67. 67. Commit Early,Commit Often
  68. 68. Commit Early,Commit Often
  69. 69. Atlassian DVCS
  70. 70. Atlassian DVCS Benefits
  71. 71. Benefit: Developer Speed• Common commands, just faster• Fast tools = happy developers• Complete history at hand
  72. 72. Benefit: Developer Speed• Common commands, just faster• Fast tools = happy developers• Complete history at hand
  73. 73. Benefit: Fast Feedback• More lessons learnt• Issues resolved more timely• Less risk and impact to a project• More in tune with customers
  74. 74. Benefit: Fast Feedback• More lessons learnt• Issues resolved more timely• Less risk and impact to a project• More in tune with customers
  75. 75. DVCS @ Atlassian
  76. 76. DVCS @ Atlassian
  77. 77. Wrap up• DVCS has great business and technical benefits• Atlassian is shaping the future of DVCS
  78. 78. Thank youblogs.atlassian.comsourcetreeapp.com blog.jr0cket.co.uk @jr0cket

×