BuckOutsideValley.pdf

Transcript

1. Buck Build outside Silicon Valley Bruno Rocha - Software Engineer +
5. Tons of developers Several apps that share components Giant codebases Developers work in very localized squads (localized changes) Valley Companies Ability to create 
 internal helper tools
7. iFood 1. 40+ Developers 2. Four apps that need to share components 3. Developers work in very specialized squads 4. Most pull requests are very localized
8. .pbxproj conflicts
9. Maintaining modules is hard
10. Huge build times
11. No project conflicts Automatic management of modules Easy way to share components
 between projects Build only what was changed, both locally and in the CI All apps in one repo Valley Companies
12. Monorepo Build Systems
13. Monorepo Build Systems
14. Bazel Build Monorepo Build Systems
15. Buck Build Monorepo Build Systems
16. App App Splash Checkout Profile Login Architecture Client Keychain … More modules = less builds!
17. Multirepos vs Monorepos App A Repo 1 App B Library C Repo 2 Repo 3
18. Multirepos vs Monorepos App A Repo 1 App B Library C
19. App A Project A App B Project B Library C Library C
20. App A Project A App B Project B Library C Library C Builds Library C, then App A
21. App A Project A App B Project B Library C Library C Builds Library C, then App A Builds Library C again, then App B
22. //MyApps:AppA Projects A/B //MyApps:AppB //MyLibs:LibraryC
23. //MyApps:AppA Projects A/B //MyApps:AppB //MyLibs:LibraryC
24. Builds Library C, then App A Builds App B only //MyApps:AppA Projects A/B //MyApps:AppB //MyLibs:LibraryC
25. Buck Caches (Rulekeys) //MyLibs:LibraryC Hash of dependencies Compiler flags Compiler version Buck version Source contents 3fb80a353db183675fd561b284bc5085
26. CI Builds PR 1 PR 2 PR 3
27. CI Builds PR 1 PR 2 PR 3 30 minutes 30 minutes 30 minutes
28. CI Builds PR 1 PR 2 PR 3
29. CI Builds PR 1 PR 2 PR 3 30 minutes 5 minutes 3 minutes Cache Cache
30. Network Cache
31. Network Cache Upload Cache Download Remote Cache
32. Creating iOS Apps with Buck Defining rules and using the build system
35. .buckconfig
36. Buck Rules (Libraries & Tests)
37. Buck Rules (Libraries & Tests)
38. Buck Rules (Libraries & Tests)
39. Buck Rules (Libraries & Tests)
40. Building Libraries //Libraries/uUserData:UserData {root}{BUCK file path}{Rule name}
41. Building Libraries //Libraries/uUserData:UserData {root}{BUCK file path}{Rule name}
42. Build Trace buck-out/logs/build.trace
43. Testing Libraries
44. Testing Libraries
45. App A Library B Library A Library D Library C Saving time while testing iFood with Xcode: All PRs tested all modules
46. App A Library B Library A Library D Library C iFood with Buck: PRs only test the affected graph Saving time while testing
47. Buck Rules (iOS Apps)
48. Buck Rules (iOS Apps)
49. Building iOS Apps buck install {rule} -r
50. Building iOS Apps buck install {rule} -r
51. Visual Studio Code + SourceKit-LSP + CodeLLDB
52. Xcode Project Generation
53. Xcode Project Generation
55. iFood’s Build/Test CI Evolution Xcode: ~32 minutes Buck + Cache: ~21 minutes Buck + Cache + Only Test Graph: ~9 minutes
56. iFood’s .pbxproj Conflicts Evolution Xcode: All the time Buck: None at all
57. iFood’s Modularization Evolution Xcode: Create a podspec
 Create an example project
 Create the files
 Add it to the podfile
 Make our CI run the example’s tests
 Hope changes won’t break the spec Buck: Just create a folder!
58. airbnb/BuckSample
59. Buck Slack
60. Buck Slack
61. #VemProiFood + swiftrocks.com @rockthebruno Obrigado!