Configuring the GitHub Hook URL
Running a MacOS SlaveNext we need to configure the Xcode build for the iOS application. Obviously, this needs to run on a MacOS slave and, in production scenarios, one would normally configure headless MacOS servers to handle the builds – however, you can easily do the same thing using a MacBook laptop, by running jenkins-cli.war in a terminal window:
This is very convenient to test out the Jenkins configuration with your local Xcode development environment. You will need to make sure your SSH keys are configured correctly, but you should just be able to use the same key pair you use for your CloudBees/Jenkins account. There are full instructions on how to run customer provided slaves with a link to download an up-to-date version of jenkins-cli.war here: http://wiki.cloudbees.com/bin/view/DEV/Customer+Provided+Slaves
Setting up Xcode iOS BuildsOnce the channel has been established (as shown in the screenshot above), you will see the new node (here it’s “markmacbook”) appear in the Jenkins console, and we are ready to configure the actual Xcode build using the Jenkins Xcode Plugin. In this example, to keep things simple, I am running jenkins-cli.war in my Xcode project directory, so most of the fields are either blank or take default values:
Distributing the Mobile App for Beta Testing
In a follow-up blog, I’ll describe how to set up continuous deployment and integration testing for the back-end services.