微软 appcenter_带有AppCenter的移动应用程序CI-不错，但可能会更好

微软 appcenter

AppCenter is one of Microsoft's offerings if you need a Continuous Integration (CI) solution for mobile apps. While Fastlane can probably be called the “industry standard” for mobile app CI software, AppCenter fills a certain niche which makes it a good option for certain use cases.

如果您需要针对移动应用程序的持续集成(CI)解决方案，则AppCenter是Microsoft的产品之一。 虽然Fastlane可能被称为移动应用程序CI软件的“行业标准”，但AppCenter占据了一定的位置，这使其成为某些用例的不错选择。

Fastlane is definitely a much more complete tool-belt than AppCenter. But, in order to qualify as being used in “CI”, it has to run somewhere other than locally on your computer. This means you have to configure both Fastlane, and an on-premise box or remote cloud infrastructure where it can run.

Fastlane绝对比AppCenter更完整。 但是，为了符合在“ CI”中使用的条件，它必须在计算机本地以外的其他位置运行。 这意味着您必须同时配置Fastlane以及可以运行它的本地盒或远程云基础架构。

I like Fastlane and all of its bells, whistles and warts. But for beginners, and developers who want to do CI securely¹, Fastlane is quite a bit more complicated than AppCenter.

我喜欢Fastlane及其所有的钟声，口哨声和疣。 但是对于想要安全地执行CI的初学者和开发人员来说，Fastlane比AppCenter复杂得多。

Compare it to AppCenter, where you pretty much only have to do two things in order to get started:

将其与AppCenter进行比较，您几乎只需要做两件事即可上手：

• Create and choose the app type in the AppCenter dashboard
  在AppCenter仪表板中创建并选择应用程序类型
• Connect the app in AppCenter to your git repository
  将AppCenter中的应用程序连接到您的git存储库

After that you can create a build configuration which already has sane defaults. Things like incrementing the build number, environment secrets and signing the build “just works”. The app will build on new commits, and you have a functioning CI in place.

之后，您可以创建已经具有默认值的构建配置。 诸如增加内部版本号，环境秘密和对内部版本进行签名等工作就可以了。 该应用程序将基于新的提交，并且您具有有效的CI。

AppCenter利基市场