hands on ios developments with jenkins

Jenkins User Conference Paris, 17 April 2012 #jenkinsconf

Hands-On iOS Developments with Jenkins

Arnaud Héritier eXo Platform

http://www.exoplatform.com

Mathieu Hausherr Octo Technology

http://www.octo.com

http://goo.gl/XWGDy 1


Polls

•  English or french ? •  Who is already doing iOS developments ? •  Who is already using JenkinsCI ? •  Who is already using JenkinsCI to manage

iOS developments ?



Arnaud Héritier "   Jenkins

–  Committer since 2010 –  Maven integration –  Xcode, Appaloosa plugins …

"   Apache Maven –  Committer since 2004 and

member of the Project Management Committee

–  Coauthor of « Apache Maven » •  published by Pearson (in

French)

" eXo platform –  Software Factory

Manager –  In charge of tools

and methods "   Contact me

–  http://aheritier.net –  Twitter : @aheritier –  Skype : aheritier

3 http://goo.gl/XWGDy


Mathieu Hausherr "   iOS

–  Developer since 2008

"   Other mobile platforms –  Android, Bada, Blackberry,

Windows Phone 7...

"   Octo Technology –  Mobile Expert –  Installation of software

factories for customers

"   Contact me –  Mail: [email protected] –  Twitter : @mhausherr



Slide legend


"   If you have a mac with XCode, follow us.

"   In this slide you have something to do.

"   In this slide we explain a workaround. Don’t be afraid by this explanation. You only need it tomorrow at home for your own Software factory.

"   Find these slides here


Hands-On iOS Developments with Jenkins

"   Concepts –  iOS specificities –  Continuous integration –  Continuous deployment

"   How to –  Step by step Jenkins server setup –  Tips & Tricks to deals with Apple’s bug

"   Hands on –  Prepare the Sample App –  Setup your Jenkins jobs –  Deploy your app on your device



CONCEPTS Goals of Jenkins-CI on iOS



Reminder: Apple application provisioning strategy

Validity Limite of devices

Apple validation Availability

Ad Hoc 1 year 100 NO Everybody

In House 1 year ∞ NO Only for

companies

App Store For life ∞ YES Everybody



Certificate management pitfalls

•  Certificate with the same name doesn’t work

•  Create specific keychains per project –  Never use default keychain

•  “security set-default” command isn’t thread safe –  Allow only one executor per server



Why automatic distribution is useful for?

•  Speedup the feedback loop with early adopters and QA Teams

•  Improve time to market –  Spend time to develop instead of distribute

•  Resign apps for certificates expiration –  Ad Hoc and In House certificates expire after one

year –  Rebuild all your app safely



Continuous integration concepts

Developer

Developer

Source code + tests

Unit tests

SenTesting

Source code + tests 1

1

2

3

Software Factory

Building application

Jenkins

Code versionning

Git

Static analysis

Clang



Continuous deployment concepts

Publish


Jenkins

Private store

Appaloosa

Download

Documentation generation

Apple doc

1

2

4

Code versionning

Git

Push

5

6

User devices

Software Factory

Archive

4 Archive

Public store

App Store Submit

5

6 Download



Appaloosa concept



Getting your device UDID We need your device UDID to be able to push apps to your device 1.  Download “UDID sender” on

the App Store 2.  Send UDID via E-Mail to

[email protected]



HOW TO Step by step guide for Jenkins-CI on iOS



Plugins installation Ø  Home Ø  Manage Jenkins Ø  Manage Plugins

Ø  Install these plugins •  Appaloosa •  Clang Scan-Build •  Git

•  Xcode



Plugins configuration •  By default Xcode plugin

settings should be good for a standard installation

•  Clang Static Analyzer binaries have to be downloaded from http://clang-analyzer.llvm.org/ and extracted on the server or agent where they’ll be used

•  In “System settings” (Clang Scan-Build Plugin part) you need to add at least one installation.



What if I soon have a Jenkins on a non Mac server? •  Why use a non Mac

Jenkins? –  Regroup all your jobs –  Maintain only one

instance of Jenkins –  Create dependencies

between mobile and not mobile projects

•  How use a non Mac Jenkins? –  Create Mac OS node –  Only need a SSH

connection


Master Node

Scheduling build

Jenkins

Code versionning

Git

MacOS Node


XCode


Node creation •  To create an agent

dedicated for xcode builds you need to create a node with : •  A label to select jobs for

which you’ll use it •  A SSH connection with a

password less private key •  The path for Clang checker

binaries



Affect job to a node •  Create a “MacOSX” label •  Force job to run on

“MacOSX”-labeled nodes



Xcode bug for iOS unit testing Source: http://www.raingrove.com/2012/03/28/running-ocunit-and-specta-tests-from-command-line.html

•  Edit your RunPlatformUnitTests

sudo vim `xcode-select -print-path`/Platforms/iPhoneSimulator.platform/Developer/Tools/RunPlatformUnitTests Replace Warning ${LINENO} "Skipping tests; the iPhoneSimulator platform does not currently support application-hosted tests (TEST_HOST set)."

By: export CFFIXED_USER_HOME="${BUILT_PRODUCTS_DIR}/UserHome/" mkdir -p "${CFFIXED_USER_HOME}" mkdir -p "${CFFIXED_USER_HOME}/Library/Caches" mkdir "${CFFIXED_USER_HOME}/Library/Preferences" mkdir "${CFFIXED_USER_HOME}/Documents" export OTHER_TEST_FLAGS="${OTHER_TEST_FLAGS} -RegisterForSystemEvents" RunTestsForApplication "${TEST_HOST}" "${TEST_BUNDLE_PATH}"



Configure your project for Unit Tests •  Check run action for your

Test target

•  Share your Scheme



Add Xcode unit testing build phase •  Commit your scheme on GIT

•  Use Scheme instead of target for testing. Use target only for building.

•  Set SDK to iphonesimulator

•  Set Configuration to Debug

•  Add TEST_AFTER_BUILD=YES in Custom xcodebuild arguments



Write a test

-  (void)test_parseRoomsFromDictionary_ !returnObjectsArrayForCorrectDictionnary!{ ! // Given! NSDictionary *dictionnary = [NSDictionary dictionaryWithObject:[NSArray array] forKey:KEY_ROOMS]; ! ! // When! NSArray* rooms = [JUCEventsService parseRoomsFromDictionary:dictionnary]; ! ! // Then! STAssertTrue([rooms isKindOfClass:[NSArray class]],nil); !}

•  Use SenTestKit Framework

•  Add Mock With OCMock



Add clang static analysis build phase •  Configure your target



Appaloosa jenkins’ integration •  Check IPA generation

•  Add Appaloosa step to your project

•  Receive Push Notification

Token: igjrz4w701ynrkzd2zwh2u450ilg00dg



Publish to the App Store

•  Apple doesn’t provide API

•  Need manual actions –  On a Mac –  Without proxy



Generate Apple Doc •  Install Apple Doc https://github.com/tomaz/appledoc

•  Command line

appledoc conf.plist <outfile>

•  Add an “aggregate” target to the project

Perform automatic doc generation locally



HANDS ON … LET’S GO Jenkins set-up, from GitHub to your device



Fork on github the sample project

http://goo.gl/alKgW And then clone your fork git clone git://github.com/XXXX/JenkinsSample.git



Setup a continuous integration job Setup Git



Setup a continuous integration job Add a Clang Scan-Build Phase



Setup a continuous integration job Add an Xcode build step to execute tests •  Use a schema (JUC Paris) •  SDK = iphonesimulator •  Config = Debug

•  Args = TEST_AFTER_BUILD=YES •  Clean test reports



Setup a continuous integration job Activate Clang and unit tests reports



Fix the test In JUC ParisTests/JUC_ParisTests.m Comment the failling test Commit and push on github git add . git commit git push Relaunch your build



Change your Bundle Id In Project Properties > JUC Paris Target > Summary Change Bundle identifier to com.jenkins.juc-paris.app.yourname Commit and push on github git add .

git commit git push



Add a deployment Job Same github settings Create an Xcode build step •  Target = JUC Paris

•  Config = Release •  Setup versions •  Build IPA •  Embedded profile



Appaloosa installation on your device

http://goo.gl/hQ2Ue



Appaloosa installation on your device Account information •  Login:

[email protected] •  Password:

jenkins



Add a deployment Job Setup Appaloosa with this token : igjrz4w701ynrkzd2zwh2u450ilg00dg



Enjoy



Thank You To Our Sponsors

Platinum Sponsor

Silver Sponsor

Gold Sponsor
