Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Speeding Up Your CI
Search
yhkaplan
March 28, 2019
Programming
520
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Speeding Up Your CI
yhkaplan
March 28, 2019
More Decks by yhkaplan
See All by yhkaplan
Using the latest UICollectionView APIs
yhkaplan
0
3.5k
Swift and Concurrency: The Plan for World Domination
yhkaplan
0
210
Backend-Driven UI: Making Screens Dynamic
yhkaplan
1
1.9k
Migrating from UIKit to SwiftUI efficiently
yhkaplan
4
3.9k
Property Wrappers
yhkaplan
0
620
Parser Combinators
yhkaplan
0
320
The Great Swift Migration
yhkaplan
1
4.3k
Automate All the Things
yhkaplan
4
2.7k
Other Decks in Programming
See All in Programming
yield再入門 #phpcon
o0h
PRO
0
1.1k
AIを紡ぐPMのお話
swdtkuy
0
110
【QA Test Talk Vol.8】AI-DLC による Whole Team Approach の加速
pkshadeck
PRO
0
200
<title><a id="</title>君はこのHTMLをパースできるか"></a></title> #雑LT_study
pizzacat83
0
150
GDG Korea Android: 2026 I/O Extended ~ What's new in Android development tools
pluu
0
230
AI時代のPHPer生存戦略 ~「言語、もうなんでもよくない?」に本気で向き合う~
vivion
0
800
仕様駆動開発へのトライを機に チームに適合する手法を模索し続けている話
freee
PRO
0
560
使いながら育てる Claude Code — 開発フローの1コマンド化 × 繰り返し指摘の自動仕組み化
shiki_kakaku
0
1.8k
ソフトウェア設計に溶けるインフラ ― AWS CDK のインフラ認識論
konokenj
3
800
複数の Claude Code が"放置"されてしまう問題をCLI ダッシュボードを自作して解決した話
sumihiro3
1
700
Claude Code全社展開のためにやったことn選~プラグイン302個・コミッター271人を支えるために~
kenchan
5
1.6k
型も通る、synthも通る、それでも危ない 〜AIのCDKの権限とコストを機械で検証する〜 / It Passes Type Checks, It Passes Synth Checks, but It’s Still Risky — Automatically Verifying Permissions and Costs in AI’s CDK —
seike460
PRO
1
570
Featured
See All Featured
SERP Conf. Vienna - Web Accessibility: Optimizing for Inclusivity and SEO
sarafernandez
2
1.6k
Introduction to Domain-Driven Design and Collaborative software design
baasie
1
940
svc-hook: hooking system calls on ARM64 by binary rewriting
retrage
2
490
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
128
56k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.6k
Fireside Chat
paigeccino
42
4k
AI Search: Implications for SEO and How to Move Forward - #ShenzhenSEOConference
aleyda
1
1.3k
The Pragmatic Product Professional
lauravandoore
37
7.4k
Taking LLMs out of the black box: A practical guide to human-in-the-loop distillation
inesmontani
PRO
3
2.3k
Navigating Algorithm Shifts & AI Overviews - #SMXNext
aleyda
1
1.6k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
2
470
Practical Orchestrator
shlominoach
191
12k
Transcript
SPEEDING UP YOUR CI 1
SELF INTRO > Joshua Kaplan > minne @ GMO Pepabo
> Danger-Swift contributer > Likes 2
WHAT DO WE USE CI FOR? 3
1. Automated testing 2. Static analysis (linting etc) 3. Beta
deployment 4. Release build deployment 4
WHAT WERE BUILD TIMES LIKE? 5
> 1st build: 55 minutes > 2nd and later: 35
minutes 6
WHAT DID THEY BECOME? 7
> 14-16 minutes 8
HOW? 9
CACHING FRAMEWORKS 10
> Moving to Carthage and using Rome > Biggest impact:
55 to 33 minutes 11
WHAT IS ROME? 12
UPGRADING PLAN 13
14
> Not much to explain here > 33 to 20
minutes 15
ONLY GETTING CODE COVERAGE WHEN TESTS CHANGE 16
> 2 minutes less 17
REMOVE POINTLESS INDEXING 18
19
> Saves 1 or 2 minutes COMPILER_INDEX_STORE_ENABLE=NO 20
OTHER TECHNIQUES I LOOK FORWARD TO 21
> Parallelization > Separate modules 22
CONCLUSION 23
MESS AROUND 24