[英]Fastlane build works from command line, not from Jenkins
I have a very simple fastlane setup: 我有一个非常简单的fastlane设置:
lane :buildonly do
build_app scheme: "MyApp", configuration: "Release", export_xcargs: "-allowProvisioningUpdates"
end
This lane works perfectly on command line completely unattended (I had to enter my credentials the first time, but now it remembers them). 该通道可以在完全无人值守的命令行上完美运行(我必须第一次输入凭据,但现在它会记住它们)。
[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! 🎉
I set up a simple Jenkins job (same machine, same user) that just clones my repo and runs the script 我设置了一个简单的Jenkins作业(同一台机器,同一用户),它只是克隆我的仓库并运行脚本
bundle install
bundle exec fastlane buildonly
and this fails pretty much immediately: 这几乎立即失败了:
[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.
What do I have to change about my Jenkins setup so that it can see the same certs as the command line? 我必须对我的Jenkins设置进行哪些更改,以便它可以看到与命令行相同的证书?
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.