Fastlane 构建从命令行工作，而不是从 Jenkins

Question

我有一个非常简单的快车道设置：

lane :buildonly do
  build_app scheme: "MyApp", configuration: "Release", export_xcargs: "-allowProvisioningUpdates"
end

这条通道在完全无人值守的命令行上完美运行(我第一次必须输入我的凭据，但现在它会记住它们(。

[16:54:39]: Successfully exported and compressed dSYM file
[16:54:39]: Successfully exported and signed the ipa file:
[16:54:39]: /Users/jenkins/MyApp/MyApp.ipa
+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
| 2    | build_app        | 594         |
+------+------------------+-------------+
[16:54:40]: fastlane.tools just saved you 10 minutes! 🎉

我设置了一个简单的 Jenkins 作业(同一台机器，同一个用户(，它只是克隆我的存储库并运行脚本

bundle install
bundle exec fastlane buildonly

这几乎立即失败：

[16:59:41]: ▸ === BUILD TARGET MyTarget OF PROJECT MyApp WITH CONFIGURATION Release ===
[16:59:41]: ▸ Check dependencies
[16:59:41]: ▸ Code Signing Error: No signing certificate "iOS Development" found:  No "iOS Development" signing certificate matching team ID "FFFFFFFF" with a private key was found.

关于我的 Jenkins 设置，我必须更改哪些内容，以便它可以看到与命令行相同的证书？

Answer 1

由于 Jenkins 是使用 launchd 运行的，我不得不将 Jenkins 用户的证书从"登录"钥匙串复制到"系统"中。

多亏了这个问题。