Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Speeding Up Your CI

yhkaplan
March 28, 2019
Programming
0
440

Speeding Up Your CI

yhkaplan

March 28, 2019
Tweet

More Decks by yhkaplan

See All by yhkaplan
Using the latest UICollectionView APIs
yhkaplan
0
2.2k
Swift and Concurrency: The Plan for World Domination
yhkaplan
0
150
Backend-Driven UI: Making Screens Dynamic
yhkaplan
1
1.6k
Migrating from UIKit to SwiftUI efficiently
yhkaplan
4
3.3k
Property Wrappers
yhkaplan
0
510
Parser Combinators
yhkaplan
0
240
The Great Swift Migration
yhkaplan
1
4k
Automate All the Things
yhkaplan
4
2.2k

Other Decks in Programming

See All in Programming
menu基盤チームによるGoogle Cloudの活用事例~Application Integration, Cloud Tasks編~
yoshifumi_ishikura
0
110
Fibonacci Function Gallery - Part 1
philipschwarz
PRO
0
210
短期間での新規プロダクト開発における「コスパの良い」Goのテスト戦略」 / kamakura.go
n3xem
2
170
良いユニットテストを書こう
mototakatsu
5
1.9k
ゆるやかにgolangci-lintのルールを強くする / Kyoto.go #56
utgwkk
1
370
今年のアップデートで振り返るCDKセキュリティのシフトレフト/2024-cdk-security-shift-left
tomoki10
0
190
モバイルアプリにおける自動テストの導入戦略
ostk0069
0
110
KMP와 kotlinx.rpc로 서버와 클라이언트 동기화
kwakeuijin
0
140
数十万行のプロジェクトを Scala 2から3に完全移行した
xuwei_k
0
270
Full stack testing :: basic to basic
up1
1
930
バグを見つけた？それAppleに直してもらおう！
uetyo
0
180
As an Engineers, let's build the CRM system via LINE Official Account 2.0
clonn
1
670

Featured

See All Featured
Art, The Web, and Tiny UX
lynnandtonic
298
20k
Fireside Chat
paigeccino
34
3.1k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
95
17k
StorybookのUI Testing Handbookを読んだ
zakiyama
27
5.3k
4 Signs Your Business is Dying
shpigford
181
21k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
32
2.7k
Building Better People: How to give real-time feedback that sticks.
wjessup
365
19k
Bash Introduction
62gerente
608
210k
GraphQLの誤解/rethinking-graphql
sonatard
67
10k
Visualization
eitanlees
146
15k
Navigating Team Friction
lara
183
15k
GraphQLとの向き合い方2022年版
quramy
44
13k

Transcript

  1. SPEEDING UP YOUR CI 1

  2. SELF INTRO > Joshua Kaplan > minne @ GMO Pepabo

    > Danger-Swift contributer > Likes 2

  3. WHAT DO WE USE CI FOR? 3

  4. 1. Automated testing 2. Static analysis (linting etc) 3. Beta

    deployment 4. Release build deployment 4

  5. WHAT WERE BUILD TIMES LIKE? 5

  6. > 1st build: 55 minutes > 2nd and later: 35

    minutes 6

  7. WHAT DID THEY BECOME? 7

  8. > 14-16 minutes 8

  9. HOW? 9

  10. CACHING FRAMEWORKS 10

  11. > Moving to Carthage and using Rome > Biggest impact:

    55 to 33 minutes 11

  12. WHAT IS ROME? 12

  13. UPGRADING PLAN 13

  14. 14

  15. > Not much to explain here > 33 to 20

    minutes 15

  16. ONLY GETTING CODE COVERAGE WHEN TESTS CHANGE 16

  17. > 2 minutes less 17

  18. REMOVE POINTLESS INDEXING 18

  19. 19

  20. > Saves 1 or 2 minutes COMPILER_INDEX_STORE_ENABLE=NO 20

  21. OTHER TECHNIQUES I LOOK FORWARD TO 21

  22. > Parallelization > Separate modules 22

  23. CONCLUSION 23

  24. MESS AROUND 24