weijia.wang
weijia.wang

Reputation: 2168

jenkins build iOS project error about 'no certificat matching .....'

My jenkins build iOS project by xcode-plugin.

jenkins and xcode7 building project is ok, but xcode8 error: enter image description here

my project configuration :

enter image description here

I had try archive project (Debug) on xcode with this config, everything is ok.

but jenkind build failed!!

next I change this config with : Automatically manage signing

jenkins build error:

enter image description here

Some people encountered such a problem? How do I solve?

Upvotes: 0

Views: 479

Answers (2)

weijia.wang
weijia.wang

Reputation: 2168

I am working on

because jenkins no permissions get identity ,jenkins log :

security find-identity -p codesigning -v
0 valid identities found

My Jenkins config in tomcat, and the tomcat automatic running by LaunchAgents, but my auto config plist in /Library/LaunchAgents, and running tomcat by system, no permissions to get identity

so let auto config plist in ~/Library/LaunchAgents, and running tomcat by user,Jenkins get all identity

Upvotes: 0

shallowThought
shallowThought

Reputation: 19602

Keychain and Provisioning Profile have to be accessible on the the build node. This Jenkins plugin helps you to copy keychain and profile to your build node. It also creates variables to reach them later on within your Jenkins job.


We observe issues with this plugin on (Jenkins) servers that are running Windows as OS though. I.e. it mistakes slashes with backslashes in paths, which renders the paths un-find-able.

In this case you have to copy the keyChain containing your certificate(s) to your build node and specify it in your build command. Before you use the keyChain, unlock it:

security unlock-keychain -p "keychain_password" "/path/to/MyKeychain.keychain"

And also the Provisioning Profile. It might be helpful to check in your profile to git. That way you have your (global) keyChain stored on the node and can reach your (project specific) Provisioning Profile in your repo and your whatever solution (e.g. xcodebuild script) generally works for all jobs, as long as the provisioning profiles path is generalized for all projects (for instance: provisioning_profiles/Release/profile.mobileprovisioning).

In this case I prefer xcodebuildover the Xcode Jenkins Plugin.

Upvotes: 0

Related Questions