We use Hudson for builds and have added the following command to our build process:
security unlock-keychain -p password ~/Library/Keychains/build.keychain
This is the first line of our shell script command in Hudson. I did try adding it as a Run Script build phase, but the trouble with that is that it's part of your normal build, whereas I wanted this command to be run only on the Hudson server, so it made more sense to include it in the Hudson configuration rather than in the normal build.
Jason On 20 Jun 2011, at 16:14, Jeff Kelley wrote: We have a Hudson server set up to automatically build our iOS applications and spit them out to a distribution server. When running and the user isn’t logged in, the login keychain must be unlocked using the security command. Is there a way to get this to work with a different keychain? I’d like to make a new keychain that only contains the bits needed to codesign the applications, but when I try to compile I get this error:
[BEROR]Code Sign error: The identity 'iPhone Developer' doesn't match any valid certificate/private key pair in the default keychain
When it’s on the default, unlocked login keychain, this works. I didn’t see anything in the xcodebuild manpage or on Google, but is there some hidden setting that allows for selecting a non-default keychain for xcodebuild?
Jeff Kelley
|