1. 2013-01-23 GREE Tech Talk＃02
Takafumi ONAKA a.k.a. @onk
1

2. Sorry
2

3. I’m not good at English.
So, I use machine translate.
3

4. Introducing myself
4

5. we're hiring
5

6. • Name:
•@onk
• Takafumi ONAKA (大仲 能史)
• Work:
• Social Game Developer
• Application Engineer
6

7. Today’s talk
7

8. In conclusion, Use github enterprise
8

9. Gitlab is «poormans github enterprise»
9

10. • 暗黒のsubversion期
• Github enterpriseを試用→挫折
• Gitlabとの出会い
• Subversionからの移行
• 俺たちの戦いはこれからだ!!
10

11. Dark ages reign of subversion
11

12. Our subversion branches
12

13. trunk
staging
release
3 main branches
13

14. trunk
staging
release
Commit to trunk
14

15. trunk
staging
release
Cherry pick & test on staging
15

16. trunk
staging
release
release
16

17. trunk
staging
release
commit
17

18. trunk
staging
release
Cherry-pick
18

19. trunk
staging
release
release
19

20. Many problems
20

21. • ブランチ作成コストが重い
cost of making a branch is high
21

22. • 数百commitの中から今回リリース
すべき100commitを見つけ、適切
にconflictを解消しつつmergeする
Cherry pick requires the skill of an artisan
22

23. • 1アプリに1人merge職人が必要に
なる
• 職人の数しかアプリを作れない
So, our make line number is limited
23

24. • 未mergeのcommit一覧を頻繁に参
照する
•`svn mergeinfo --show-revs eligible`
Fat svn:mergeinfo
24

25. • 遅い
• Disk IO食いすぎ
• 遅い
Slow, slow, slow
25

26. want to use git
26

27. Try github enterprise
27

28. 28

29. less use
29

30. The tragedy "only I use git, others use svn"
30

31. Why failure?
31

32. Branch strategy mismatch
32

33. Shift of application under running is difficult
33

34. Long long time of using subversion
made the track record.
34

35. “its running”, we get less happiness if shift
35

36. メリット デメリット
・速い ・200アカウント
・Pull request駆動 分の初期コスト
開発 ・教育コスト
・今風で嬉しい ・移行期の運用速
度低下
Merit / Demerit
36

37. メリット デメリット
文化 金
Merit is “Culture”, Demerit is “Money”
37

38. Can’t measure culture to money
38

39. Certainty is missing to make culture
39

40. Use github enterprise request is rejected
40

41. Use git without initial cost
41

42. I want to use git and get git cultures
42

43. How to start using git without initial cost
43

44. Find “gitlab”
44

45. • Github likeなweb UI
• 管理もweb UIで可能
• Pull request機能があるもの
• 今後数年主流になりそうなもの
Basis of selection:
Web UI & pull request
45

46. When using except github
select language and a framework maintainable
by two or more persons.
46

47. i have to continue eating dog food.
47

48. It will fail, if a maintainer is fixed
48

49. Gitlab is made by Ruby on Rails
49

50. 80 ruby engineers are in our company.
50

51. We can maintain if modern Rails application
51

52. Gitlab is on latest rails and modern libraries
52

53. It uses with some corrections
53

54. Judged satisfactory
54

55. no necessity if there is even money
55

56. subversion to gitlab
56

57. Learn from a failure,
and make shift strategy
57

58. Cross commit by git-svn
58

59. git
topic topic
master
subversion
trunk
59

60. Not change release flow during the combined use.
60

61. let everyone used to use git in this period
61

62. Can release without cherry-pick, throw away svn
62

63. 63

64. `git svn fetch` needs some weeks
64

65. • 全プロジェクトを全ユーザが閲覧
可能に
• README.mdの表示
The features we added to gitlab
- Authentication change
65

66. • git-svnによるクロスコミット
• Merge Requestにdescription追加
- Cross commit by using git-svn
- Add description for “merge request”
66

67. • Push時にIssue/MRに紐づける
• 監視
- Commit to issue relations
- Supervises
67

68. no necessity if there is even money
68

69. • Commit mail
• 各種通知bot
Make some notify bot for git
69

70. There is more pleasant than making the tool for svn
70

71. More improvement!
71

72. Sorry
72

73. Now is during the combined use
73

74. Feeling from using gitlab
74

75. I’m sure “pull request is JUSTICE”
75

76. I waited for this flow very long
76

77. Conclusion
77

78. • サーバに入れる
• Gitリポジトリを直接操作可能
• 柔軟な移行手順を踏める
Gitlab’s merit
- Can log in to server
- flexible shift procedure can be used
78

79. • Pull requestのない環境で文化を作
るのは難しい
• gitlabで文化を作れるようになっ
た
• GHEであればしなくてもいい苦労
はあるが、gitlabは妥当な代替
79

80. Thank you
80

81. 81