This document discusses continuous integration from unit tests to hardware. It describes how continuous integration helps ensure quality by automatically building and testing software anytime code changes are committed. The speaker's company Forget Box uses Jenkins for continuous integration to build and test their iOS app daily. Plugins and scripts can be used in Jenkins to run unit tests, compute code coverage, package apps, and deploy to test devices. Continuous integration helps developers catch bugs early and "never break the build again."

1. CONTINUOUS
INTEGRATION
FROM UNIT TESTS
TO HARDWARE
Rémy Virin
Cocoaheads
@remyvirin

2. WHO AM I ? LIMA ?
• I’m an iOS software engineer at Forget box.
• We’re creating a new way to store your data.
• Backed on kickstarter
• 12,8K backers
• $ 1,2 Millions

3. BEFORE, 10 YEARS AGO
One User
One device
One Memory

4. TODAY, MULTIPLE DEVICES,
MULTIPLE MEMORIES
One User
Multiple devices
Divided memories

5. TODAY, CLOUD SOLUTION IS
JUST A PATCH
One User
Multiple devices
Divided memories

6. TODAY, CLOUD SOLUTION IS
JUST A PATCH
One User
One Unified Memory

7. CONTINUOUS
INTEGRATION
FROM UNIT TESTS
TO HARDWARE

8. WHY ?

10. SHIP, SHIP, SHIIIIP
SHIP, SHIP, SHIIIIP !!!
!!!

11. MEASURE QUALITY
• Photo quality

12. HOW ?

13. C.I. BASICS
Execute unit
tests
Publish app to
mktg
Continuous
Integration
Fetch sources
Generate
Documentatio
n
Workstations
Generate metrics
Execute functional tests

14. SAS vs LOCAL

15. JENKINS

16. ABOUT JENKINS
• Open Source
• Easy to install
• Best known CI solution

17. INSTALL JENKINS

18. ADD PLUGINS

19. ADD PLUGINS

20. CREATE A JOB
CREATE A JOB

21. CREATE A JOB
• Set up Github url and restrict where the job should be run if your
mac is a node of Jenkins.

22. CREATE A JOB WITH
PLUGINS

23. CREATE A JOB WITH A
SCRIPT
Build your project, run Unit Tests, compute code coverage, package
your app, deploy it etc…
$ pod install
$ xcodebuild -workspace Lima.xcworkspace -scheme "Lima"
-destination=build -configuration Debug_deploy -sdk
iphoneos7.0 ONLY_ACTIVE_ARCH=YES clean build archive
$ xcodebuild -exportArchive -exportFormat "IPA" archivePath "$NEW_ARCHIVE" -exportPath ./Lima.ipa exportProvisioningProfile "Lima Adhoc Distribution"
# And then upload to testflight via curl
Full script here: https://gist.github.com/rvirin/7796647

24. PLUGINS vs SCRIPTS
Most of the time, plugins are easier to
use. Sometimes we don’t have other
choices to use plugins
Examples :
• cocoapods plugin if podFile is not in
root folder
• run Unit tests with Xcode plugin

25. THAT’S IT, YOU CAN ENJOY
NOW…

26. AND ONE DAY, THE BUILD
FAIL !

27. WE NEED TO KNOW WHEN
BUILD FAILED
• Basic Alert : Email
• Growl Notification : Hudson-on-cocoa
• Or you can connect Jenkins to your real
life…

28. YOU’LL NEVER BROKE THE
BUILD AGAIN !
Code source : https://github.com/codedance/Retaliation

29. BOTS ON iOS

30. SETUP - REQUIREMENTS
• A mac (at least 10.9)
• OS X Server
• Xcode

31. SETUP
• Install OS X Server and Xcode on your
mac
• Activate Xcode as a service of your server
• Connect to remote repository
• Create your first bot

32. ERRORS DURING SETUP
• Error on getting source code -> no error,
big logs for nothing
• Add _teamserver public key to your Github
repository (deploy keys)

33. ERRORS DURING SETUP
• CodeSign error: code signing is required
for product type 'Application' in SDK 'iOS
7.0’  just trying to build the app !
•  Get your provisionning profile on the
mac server (Add your account to Xcode)

34. SETUP
• If you have to install your pods before
building your app :
• $ sudo visudo -f /etc/sudoers
• Add this line :
# Same thing without a password
# %wheel
ALL=(ALL) NOPASSWD: ALL
%_teamsserver ALL=(ALL) NOPASSWD: ALL

35. • v
Source : Cocoapods mailing list

36. PODS IN XCODE
•

37. PODS IN XCODE
•

38. COOL THINGS ON BOTS
• Bots Can be created and monitored from
Xcode.
• Integrate with Xcode
• UI and UX rocks.

39. BAD THINGS ON BOTS
• Lots of bugs
• Fetching pods before building app is painfull
• No 3rd party integration (Testflight, hockeyapp
etc…)
• Can’t Archive an app
• Need to create a specific scheme

40. SONAR
An open source platform for
Continuous Inspection of code
quality

41. SONARQUBE
•

42. SONARQUBE
• Issues with OCLint are powerfull
• Generate Documentation, Count lines of
code, analyze code duplication and run Unit
Tests !
• https://github.com/octo-technology/sonarobjective-c

43. NEXT STEP : HARDWARE
NEXT STEP : HARDWARE

44. CONCLUSION

45. IMPROVEMENTS
• « Thanks to Jenkins I’m able
to test the last version of our
app just by pressing a button,
it’s awesome ! » Alex Product
Guy at Lima

46. IMPROVEMENTS
• « Each day at 4pm, we get a
new build of our app, it’s really
efficient to reduce the amount
of bugs » Tester at Meetic
(Dating website)

47. COST : 8 to 10 % of the project

48. THANKS !