title: Jenkins/Hudson Upload to Testflight
body: <p>I have a jenkins job using xcode to build my ipa file. That is all working great. Right now I just have the Marketing version set to <code>${BUILD_ID}</code> and the technical version set to <code>${BUILD_NUMBER}</code>. I also have Release configuration specified and my job is set to archive the ipa files as a post build action. I believe those combination of settings causes my resulting IPA file to be the following:</p>
  
  <pre><code>Target-Configuration-BUILD_NUMBER.ipa
  </code></pre>
  
  <p>So if my target was named BillyBob and this was the 23rd successful build, my resulting .ipa file is:<code>BillyBob-Release-23.ipa</code></p>
  
  <p>I want to setup a job or post-build action to upload my file to testflight on a successful build.</p>
  
  <p>I can not figure out what to set the file parameter of the testflight API to so that it will always find the latest build file, I don't think there is a wildcard available or if there is I don't know how to set it.</p>
  
  <p>Originally, when I wasn't setting the technical version as part of the build I had it just pointed to the <code>-1.0.ipa</code> version of the file it was creating and that would get uploaded fine.</p>
  
  <p>I've tried using both the testflight plugin for jenkins and just a curl shell script command.</p>
  
  <p>I will also point out that I'm not an iOS developer, I've just been trying to help the project by setting up the automated build, so my guess as to how that file is getting generated could be way off.</p>
  
  <p>***UPDATE
  So it looks like this current open issue is kind of what I am looking for
  <a href="https://issues.jenkins-ci.org/browse/JENKINS-13929?page=com.atlassian.jira.plugin.system.issuetabpanels%3achangehistory-tabpanel" rel="nofollow">jenkins issue section</a></p>
  
  <p>For now, I just had my job specify an output path that is the workspace of my upload to testflight job.</p>
  
  <p>It looks like in the Testflight app, if you don't specify anything for the IPA file, it looks for one in the workspace directory of that job. So I could probably also put in a request to the testflight plugin to allow you to specify a path in the IPA setting and have it find the .ipa file in that path, that currently does not work.</p>
  
  <p>If I was better at scripting I could probably also handle it in a shell command using the curl command to upload to testflight.</p>