Great! I'm glad there is no problem building iOS applications using Jenkins. The only funny thing is that plenty of people seem to have trouble with it even though it is so easy.
I have a couple of follow-up questions: You mention $PASSWORD needed to unlock the keychain. Since Jenkins Mac installer creates the "jenkins" user with no password and with login disabled, you have probably done some additional customization? What did you need to do? Change login shell? Change password? Did you also need to set up something in the jenkins user's home directory? mkdir Library? Thanks, -- Sami 2012/4/5 kenstir <kens...@gmail.com>: > I don't have any problem signing code with my iOS build fired by Jenkins. I > think it is straightforward if not easy. I did not need to modify Jenkins > in any way. My setup is: > - linux master fires osx slave using SSH > - osx slave runs as user jenkins > - user jenkins has the signing cert loaded into its keychain > - user jenkins must allow access to the signing cert. In the Keychain > Access application, right-click on "XXX private key", choose Get Info, click > Access Control, select "Allow all applications to access this item". > - key step here: build sh script executes this command: > security unlock-keychain -p $PASSWORD ~/Library/Keychains/login.keychain > > Hope that helps, > Ken
