iTunesConnect TestFlight的iOS应用版本和内部版本号 [英] iOS app version and build numbers for iTunesConnect TestFlight

问题描述

我的问题与 iTunes Connect 中对版本和内部版本号的限制有关.我们只允许使用3个非负整数，并且内部版本号必须是递增的.

My question relates to the restrictions in iTunes Connect for Version and Build number. We are only allowed 3 non-negative integers and the Build number has to be incremental.

我正在设置 Jenkins 作业，以将我的构建自动上传到 iTunes Connect ，以便测试人员可以下载它们.

I am setting up a Jenkins job to automatically upload my builds to iTunes Connect so that testers can then download them.

问题:我们如何确保递增的内部版本号?即使我们在每次提交之前都在Xcode中手动更改了它(这似乎是错误的)，也有多个开发人员在项目上工作，所以也无法在团队中同步所有提交和增量编号.

Problem: How do we ensure an incremental build number? Even if we did manually change it in Xcode before every commit (which seems wrong) there are more than one dev working on the project so there is no way we can all sync our commits and incremental numbers across the team.

很高兴:我的团队在多个分支机构工作.如果可以在Build字段中指定分支名称或其他描述，将会很有帮助.在独立的测试飞行"(将于2015年2月下旬弃用)中，我们可以上传带有一些字母的版本.

Nice to have: My team works in several branches. It would be helpful if I could specify the branch name or some other description in the Build field. In the stand alone Test Flight (to be deprecated end of Feb 2015), we could upload a build with some letters.

在这里喜欢一些输入内容！

Would love some input here!

如果iTunes Connect Test Flight不是分发测试版本的答案，那么人们还在使用哪些其他服务?

And if iTunes Connect Test Flight is not the answer to distribute test builds, what other services are people using?

谢谢！

推荐答案

在Jenkins中，有一个$ BUILD_NUMBER参数可以持续工作.您可以将其附加到info.plist中的内部版本号参数的末尾.如果info.plist中内部版本号的开头是3.1.那么您的实际内部版本号将从Jenkins变为3.1.$ BUILD_NUMBER.有一个名为plist_buddy( https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man8/PlistBuddy.8.html )，您可以使用它来编辑info.plist文件.

In Jenkins there is a $BUILD_NUMBER parameter that lasts the life of the job. You can append this to the end of the build number parameter in the info.plist. If the beginning of the build number in info.plist is 3.1. then your real build number becomes 3.1.$BUILD_NUMBER from Jenkins. There's a program called plist_buddy (https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man8/PlistBuddy.8.html) which you can use to edit the info.plist file.

序列中是否有间隔只要增加就没有关系. 3.1.部分将由人工管理，以便潜在开发人员在发布开始时就增加该部分.该方法假设您有1个工作要做.如果您有多个工作在做同一个应用程序，则可以使用Unix格式的日期/时间之类的东西，它的数量很大，通常不会倒退.

It really doesn't matter if there are gaps in the sequence as long as it's incrementing. The 3.1. part would be manually managed so that the lead developer increments that at the beginning of a release. This approach assumes that you've got 1 job to do the build. If you have multiple jobs doing builds of the same app you could possibly use something like the date/time in Unix format, it's a large number and usually doesn't go backwards.

这篇关于iTunesConnect TestFlight的iOS应用版本和内部版本号的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！