Github Enterprise じゃなくてもいいじゃん

27,441 views

Published on

GREE Tech Talk #02
GitHub:E Casual Talk
http://techtalk2.labs.gree.jp/

1 Comment
84 Likes
Statistics
Notes
  • Gitlabのメンテタイムが日本の夕方じゃなきゃ、何も問題ないのに。
    開発真っ只中の切羽詰まった状況→「これから一時間後、メンテが始まります」→なん・・・だと・・・!?
    のコンボが辛い。
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
27,441
On SlideShare
0
From Embeds
0
Number of Embeds
1,072
Actions
Shares
0
Downloads
66
Comments
1
Likes
84
Embeds 0
No embeds

No notes for slide

Github Enterprise じゃなくてもいいじゃん

  1. 1. 2013-01-23 GREE Tech Talk#02Takafumi ONAKA a.k.a. @onk 1
  2. 2. Sorry 2
  3. 3. I’m not good at English.So, I use machine translate. 3
  4. 4. Introducing myself 4
  5. 5. were hiring 5
  6. 6. • Name: •@onk • Takafumi ONAKA (大仲 能史)• Work: • Social Game Developer • Application Engineer 6
  7. 7. Today’s talk 7
  8. 8. In conclusion, Use github enterprise 8
  9. 9. Gitlab is «poormans github enterprise» 9
  10. 10. • 暗黒のsubversion期• Github enterpriseを試用→挫折• Gitlabとの出会い• Subversionからの移行• 俺たちの戦いはこれからだ!! 10
  11. 11. Dark ages reign of subversion 11
  12. 12. Our subversion branches 12
  13. 13. trunkstagingrelease 3 main branches 13
  14. 14. trunkstagingrelease Commit to trunk 14
  15. 15. trunkstagingrelease Cherry pick & test on staging 15
  16. 16. trunkstagingrelease release 16
  17. 17. trunkstagingrelease commit 17
  18. 18. trunkstagingrelease Cherry-pick 18
  19. 19. trunkstagingrelease release 19
  20. 20. Many problems 20
  21. 21. • ブランチ作成コストが重い cost of making a branch is high 21
  22. 22. • 数百commitの中から今回リリース すべき100commitを見つけ、適切 にconflictを解消しつつmergeするCherry pick requires the skill of an artisan 22
  23. 23. • 1アプリに1人merge職人が必要に なる• 職人の数しかアプリを作れない So, our make line number is limited 23
  24. 24. • 未mergeのcommit一覧を頻繁に参 照する •`svn mergeinfo --show-revs eligible` Fat svn:mergeinfo 24
  25. 25. • 遅い• Disk IO食いすぎ• 遅い Slow, slow, slow 25
  26. 26. want to use git 26
  27. 27. Try github enterprise 27
  28. 28. 28
  29. 29. less use 29
  30. 30. The tragedy "only I use git, others use svn" 30
  31. 31. Why failure? 31
  32. 32. Branch strategy mismatch 32
  33. 33. Shift of application under running is difficult 33
  34. 34. Long long time of using subversion made the track record. 34
  35. 35. “its running”, we get less happiness if shift 35
  36. 36. メリット デメリット・速い ・200アカウント・Pull request駆動 分の初期コスト開発 ・教育コスト・今風で嬉しい ・移行期の運用速 度低下 Merit / Demerit 36
  37. 37. メリット デメリット 文化 金Merit is “Culture”, Demerit is “Money” 37
  38. 38. Can’t measure culture to money 38
  39. 39. Certainty is missing to make culture 39
  40. 40. Use github enterprise request is rejected 40
  41. 41. Use git without initial cost 41
  42. 42. I want to use git and get git cultures 42
  43. 43. How to start using git without initial cost 43
  44. 44. Find “gitlab” 44
  45. 45. • Github likeなweb UI• 管理もweb UIで可能• Pull request機能があるもの• 今後数年主流になりそうなもの Basis of selection: Web UI & pull request 45
  46. 46. When using except githubselect language and a framework maintainable by two or more persons. 46
  47. 47. i have to continue eating dog food. 47
  48. 48. It will fail, if a maintainer is fixed 48
  49. 49. Gitlab is made by Ruby on Rails 49
  50. 50. 80 ruby engineers are in our company. 50
  51. 51. We can maintain if modern Rails application 51
  52. 52. Gitlab is on latest rails and modern libraries 52
  53. 53. It uses with some corrections 53
  54. 54. Judged satisfactory 54
  55. 55. no necessity if there is even money 55
  56. 56. subversion to gitlab 56
  57. 57. Learn from a failure,and make shift strategy 57
  58. 58. Cross commit by git-svn 58
  59. 59. git topic topicmaster subversiontrunk 59
  60. 60. Not change release flow during the combined use. 60
  61. 61. let everyone used to use git in this period 61
  62. 62. Can release without cherry-pick, throw away svn 62
  63. 63. 63
  64. 64. `git svn fetch` needs some weeks 64
  65. 65. • 全プロジェクトを全ユーザが閲覧 可能に• README.mdの表示 The features we added to gitlab - Authentication change 65
  66. 66. • git-svnによるクロスコミット• Merge Requestにdescription追加 - Cross commit by using git-svn- Add description for “merge request” 66
  67. 67. • Push時にIssue/MRに紐づける• 監視 - Commit to issue relations - Supervises 67
  68. 68. no necessity if there is even money 68
  69. 69. • Commit mail• 各種通知bot Make some notify bot for git 69
  70. 70. There is more pleasant than making the tool for svn 70
  71. 71. More improvement! 71
  72. 72. Sorry 72
  73. 73. Now is during the combined use 73
  74. 74. Feeling from using gitlab 74
  75. 75. I’m sure “pull request is JUSTICE” 75
  76. 76. I waited for this flow very long 76
  77. 77. Conclusion 77
  78. 78. • サーバに入れる• Gitリポジトリを直接操作可能• 柔軟な移行手順を踏める Gitlab’s merit - Can log in to server- flexible shift procedure can be used 78
  79. 79. • Pull requestのない環境で文化を作 るのは難しい• gitlabで文化を作れるようになっ た• GHEであればしなくてもいい苦労 はあるが、gitlabは妥当な代替 79
  80. 80. Thank you 80
  81. 81. 81

×