title: Apple CI / Xcode Service and Jenkins
body: <p>Is there a way/plugin to integrate the new Xcode service and/or the new Apple CI with Jenkins?</p>
  
  <h2>Why?</h2>
  
  <p>A main issue with having a Jenkins server + an OSX build slave connected via <code>ssh</code> is that <strong>Unit Tests do not work</strong>, as the iOS Simulator needs a graphical environment which is not present in this configuration.</p>
  
  <p>I hope that it is possible to integrate the Xcode service (which supports Unit Testing) with Jenkins.</p>
  
  <p>It could be that using the Apple CI will be enough for my needs, but this question aims at the <strong>integration of the Xcode service with Jenkins</strong>.</p>
  
  <h2>What I do already know</h2>
  
  <p>I have experience with the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Xcode+Plugin">existing Xcode Jenkins plugin</a>, but it seems not to support the brand new Xcode service or the new Apple CI. I'm especially keen on unit testing via CI (which did not work properly over a ssh session with the old way).</p>
  
  <h2>What I want to know</h2>
  
  <p>I'd like info on the following issues currently not working with Jenkins and an <code>ssh</code> connected build slave:</p>
  
  <ul>
  <li>Unit Tests on a headless system</li>
  <li>Acceptance tests with <a href="http://www.testingwithfrank.com/">Frank</a> or similar</li>
  <li>Automatic Provisioning Profile updating (Apple CI does that)</li>
  </ul>
  
  <p>And info on things that currently do work fine with Jenkins and an <code>ssh</code> connected build slave and still should work with an Xcode service integration:</p>
  
  <ul>
  <li>Builds of different build configurations (Release, Debug, TestFlight) / schemes</li>
  <li>Automatic Build number increment
  <ul>
  <li>(With Jenkins I can set the build number in my project to <code>${BUILD_NUMBER}</code>, and Jenkins sets this environment variable according to its build number. When the Apple CI does the builds most probably it will set the build number instead.)</li>
  <li>Handling/synchronization of Build number between Jenkins &amp; Apple CI</li>
  </ul></li>
  <li>Accessing build products of the Apple CI from different Jenkins Jobs
  <ul>
  <li>e.g. for a Job to upload to TestFlight</li>
  </ul></li>
  <li>Backup of builds</li>
  <li>Automatic builds on git push to a specific branch</li>
  <li>E-Mail notifications</li>
  </ul>
  
  <h2>Some additional questions/hints</h2>
  
  <ul>
  <li>I'm not sure whether the <code>Apple CI == Xcode service</code> or if the Apple CI just <em>uses</em> the Xcode service. In the latter case the Xcode service just would be like an intelligent build slave, and Jenkins maybe could use that to do builds and tests, but manage build numbers and products by itself.</li>
  <li>I'm aware that the Apple CI is an separate CI, and integrating several CIs with each other is not the most easy or useful way to go. I just fear that the Apple CI is not flexible enough for my needs (see above), and that the old way with Jenkins bears some problems (see above).</li>
  </ul>