如何在 xcode 4 中完全自动化从构建到 .ipa 文件
在 xcode 3 中，使用 bash 脚本，我可以从命令行运行 xcode，然后获取构建目录中的文件并将它们压缩到 .ipa 文件中，从而为我的 adhoc iOS 发行版实现完全自动化的构建过程。任何时候只要有人为干预，就有可能出现错误。
在 xcode 4 下，这似乎不再可能了。构建目录已替换为 DerivedBuilds 文件夹，并且它使用一些混淆命名，因此不可能让外部脚本找到这些文件。
在 xcode 4 中，构建后，我需要运行 Produce->Archive，然后在管理器中选择文件，然后选择保存，然后导航到最终文件夹并命名文件并点击保存。这是一个非常容易出错的过程，最好留给机器来完成。
那么，有没有办法从干净的构建一直到签名的 .ipa 文件？我必须相信这是可能的，具有自动化构建流程的人们不可能必须手动执行此步骤。
有谁知道该怎么做？
In xcode 3, using a bash script, I could run xcode from the command line, then take the files in the build directory and zip them up into a .ipa file, allowing for a fully automated build process for my adhoc iOS distribution. Anytime there is human intervention, there is the possibly for error.
Under xcode 4, this seem to be not possible anymore. The build directory has been replaced with a DerivedBuilds folder and it uses some obfuscation naming, so it's not possible to let an external script find the files.
In xcode 4, after the build, I need to run Produce->Archive, then selected the file in the organizer, then select save, then navigate to the final folder and name the file and hit save. This is a very error prone process better left to machines.
So, is there a way to go from a clean build all the way to a signed .ipa file? I've got to believe this is possible, there is no way people with automated build processes are having to do this step by hand.
Does anyone know how to do this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当然，我在持续集成环境中使用的脚本可以在 https://gist.github.com/949831 获取 这可能会超出您的需要，但应该能够作为您想要包含在构建过程中的任何步骤的基础。
正如您所指出的，很难预测 Xcode 将使用的派生数据路径，但将其作为构建脚本的一部分定位在构建输出中并不难。
Sure, the script I have been using in my continuous integration environment is available at https://gist.github.com/949831 That might do more than you need but should be able to serve as a base for whatever steps you want to include in your build process.
As you noted it would be hard to predict the derived data path Xcode will use but it is not too hard to located it in the build output as part of the build script.