SPEEDING UP YOUR CI1
View Slide
SELF INTRO> Joshua Kaplan> minne @ GMO Pepabo> Danger-Swift contributer> Likes2
WHAT DO WE USE CI FOR?3
1. Automated testing2. Static analysis (linting etc)3. Beta deployment4. Release build deployment4
WHAT WERE BUILD TIMES LIKE?5
> 1st build: 55 minutes> 2nd and later: 35 minutes6
WHAT DID THEY BECOME?7
> 14-16 minutes8
HOW?9
CACHING FRAMEWORKS10
> Moving to Carthage and using Rome> Biggest impact: 55 to 33 minutes11
WHAT IS ROME?12
UPGRADING PLAN13
14
> Not much to explain here> 33 to 20 minutes15
ONLY GETTING CODE COVERAGE WHEN TESTS CHANGE16
> 2 minutes less17
REMOVE POINTLESS INDEXING18
19
> Saves 1 or 2 minutesCOMPILER_INDEX_STORE_ENABLE=NO20
OTHER TECHNIQUES I LOOK FORWARD TO21
> Parallelization> Separate modules22
CONCLUSION23
MESS AROUND24