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
今年のアップデートで振り返るCDKセキュリティのシフトレフト/2024-cdk-security-shift-left
tomoki10
0
200
テストコードのガイドライン 〜作成から運用まで〜
riku929hr
4
590
Amazon S3 NYJavaSIG 2024-12-12
sullis
0
100
Symfony Mapper Component
soyuka
2
730
責務を分離するための例外設計 - PHPカンファレンス 2024
kajitack
6
1.1k
rails statsで大解剖 🔍 “B/43流” のRailsの育て方を歴史とともに振り返ります
shoheimitani
2
940
各クラウドサービスにおける.NETの対応と見解
ymd65536
0
100
テストコード書いてみませんか？
onopon
2
120
モバイルアプリにおける自動テストの導入戦略
ostk0069
0
110
KubeCon + CloudNativeCon NA 2024 Overview at Kubernetes Meetup Tokyo #68 / amsy810_k8sjp68
masayaaoyama
0
250
「Chatwork」Android版アプリを 支える単体テストの現在
okuzawats
0
180
ゆるやかにgolangci-lintのルールを強くする / Kyoto.go #56
utgwkk
2
390

Featured

See All Featured
Embracing the Ebb and Flow
colly
84
4.5k
Docker and Python
trallard
42
3.1k
A better future with KSS
kneath
238
17k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
45
2.2k
Music & Morning Musume
bryan
46
6.2k
Statistics for Hackers
jakevdp
796
220k
The Straight Up "How To Draw Better" Workshop
denniskardys
232
140k
Art, The Web, and Tiny UX
lynnandtonic
298
20k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
28
9.1k
Adopting Sorbet at Scale
ufuk
73
9.1k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
5
450
Build The Right Thing And Hit Your Dates
maggiecrowley
33
2.4k

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