A step-by-step tutorial for continuous integration with Jenkins for a Red Hat Mobile Native iOS application-Part 2

Part 2: How to Setup Jenkins to build iOS .ipa and run unit tests.

A robust and agile mobile application development environment requires continuous integration and delivery. It also requires an integrated and automated unit testing process that helps bring applications to market successfully. This two-part series details my work done at Red Hat Open Innovation Labs and as a Mobile Technical Account Manager to capture these mobile innovations in a useful, repeatable way. In part one of this two-part series, I broke down the steps to create and unit test a native iOS application using Red Hat’s Mobile Application Platform. In part two, I’ll show how Jenkins can be used to automate continuous integration and unit testing of that Mobile app.

Requirements

1. Xcode 7.3
2. Jenkins
3. Mac OSX El Capitan

// Fix Jenkins user

After installing Jenkins we need to setup the Jenkins user

1. In mac, go to system-preferences-Users and Groups-unlock-right click on the empty user you see. Specify Full name, and reset the password. Now we have a valid Jenkins user.

2. Run these commands to give Jenkins admin rights and add to developer group

sudo dseditgroup -o edit -a jenkins -t user admin

sudo dscl . append /Groups/_developer GroupMembership jenkins

Move your iPhone developer certificates to system.

Since Jenkins will be running as a system process, not as a user application, we need to give it access to the developer certificates.

1. Using Keychain application, find your iPhoneDeveloper certificate in login
2. Make sure to expand it to see the iOS developer part
3. Select both and copy
4. Select system and paste those two items

Logout and Login into your mac machine as Jenkins user

Add the following plugins to Jenkins

1. Git
2. Xcode Integration
3. Junit Plugin

Add SSH keys to jenkins

Add Credentials needed to do git clone. Under Credentials create a new system credential. Specify the username (same as in Red Hat Mobile Application Platform portal) and you can either generate new ssh keys or copy paste a key directly. Keep passphrase empty.

Change Xcode build folder

The new Xcode places the builds in a common folder that the Xcode plugin has issues getting to, so we need to make it relative to the workspace.

1. Go to Xcode--->Preferences---> Locations
2. For Derived Data select as shown below

Run Jenkins as Agent

In order for Jenkins to launch the simulator, it needs to be running as an Agent and not as a daemon. Follow these steps:

1. sudo cp /Library/LaunchDaemons/org.jenkins-ci.plist /Library/LaunchAgents/org.jenkins-ci.plist
2. sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist
3. sudo launchctl load /Library/LaunchAgents/org.jenkins-ci.plist

Setup a new Jenkins item

Create a new Jenkins project using freestyle option and the following settings. We actually need two build steps as you will see one for *.ipa and one for running unit tests on simulator.

1. Give your project a name.
2. Select Git, paste the git url from Red Hat Mobile Application Platform and select the right credentials.
3. Make sure the right branch is selected, here we have master

4. We need three build steps:
5. Execute shell for running pod install since our Red Hat Mobile Application Platform template uses pods

2. First Xcode build step to build and archive *.ipa
3. Select Clean before build
4. Select Generate archive
5. Set Configuration for Debug
6. Select Pack application and build ipa
   1. ${BUILD_DATE} for ipa filename
   2. Output directory to artifacts

3. Advanced Xcode build options
4. Xcode Schema File to helloword-ios-app
5. Xcode Workspace File to helloworld-ios-app
6. Build output directory /Users/Shared/Jenkins/Home/workspace/iOSBuildAndTest/DerivedData

4.Second build step for running unit tests

1. Specify Target to limit it to testing: helloworld-ios-appTest
2. Clean before build NO ← make sure this is NO or else it deletes the artifacts
3. Configuration Debug

Advanced Xcode build options

1. Clean test reports = yes
2. Xcode Schema file: helloworld-ios-app
3. SDK = iphonesimulator
4. Custom xcodebuild arguments=  test -destination 'platform=iOS Simulator,name=iPhone 6s,OS=9.3'
5. Xcode Workspace file = helloworld-ios-app

Post build steps

1. Add Archive the artifacts and place the url to DerivedData/artifacts/*.ipa
2. Add Publish JUnit test result report specify url to test-reports/*.xml

Results should look like this

This concludes part two of our tutorial for setting up Jenkins to build iOS native applications. In part one of our tutorial we added unit tests to our Red Hat Mobile Application Platform native iOS application.

Juana Nakfour is a Senior Mobile Technical Account Manager with over 15 years advanced R&D experience in the telecommunications industry. Juana’s focus is broad and include wireless communication networks, embedded/mobile devices and microservices.

A Red Hat Technical Account Manager (TAM) is a specialized product expert who works collaboratively with IT organizations to strategically plan for successful deployments and help realize optimal performance and growth. The TAM is part of Red Hat’s world class Customer Experience and Engagement organization and provides proactive advice and guidance to help you identify and address potential problems before they occur. Should a problem arise, your TAM will own the issue and engage the best resources to resolve it as quickly as possible with minimal disruption to your business.