Mobile CD

This year we created Continuous Integration (CI) for CHECK, but since last month we also are in the process of creating an automated build for our mobile projects. In the DEVOPS and Agile world we call this Continuous Delivery (CD). Why would we do this? Mainly for trying to speed up delivery of applications and in shorter iterations. We noticed in the initial projects we lost a lot of time because of deployment issues, especially with all the different App Stores around.

So we tried to use our existing CI platform. This was quite a challenge, because for instance Apple devices require some specific tools on the OS X platform, and our Jenkins CI server is running on Linux. Fortunately Jenkins also works with a master-slave model, so you can setup a Mac computer as a slave to the master build server. This way we have been able to run building and signing of iOS apps on our Mac mini and storing the results in the software repository of our Configuration management system in Confluence.

Mobile Development workflow