Hi,

I have recently set up Jenkins 1.488, and the Xcode Plugin, on a Mac Mini
with OSX Server.
I run using the default deamon mode (user jenkins).

I also followed the instructions on
http://stackoverflow.com/questions/9245149/jenkins-on-os-x-xcodebuild-gives-code-sign-error.
(I had to run security list -s ~/Library/Keychains/jenkins.keychain after
creating it in order to enable it.)

Now, when I run a build, it fails with a code-sign error:

          Code Sign error: No unexpired provisioning profiles found that
contain any of the keychain's signing certificates

Many devs seem to have had the same issue, fixed by re-downloading the
provisioning profiles and/or creating new certificates. The strange thing,
though, is that when I log on to jenkins' desktop I can build from Xcode,
and it also works when I log on using 'su - jenkins' in Terminal, so there
can't really be anything wrong with my files. Right?

What works differently in Jenkins (or the Xcode Plugin) than under 'su -
jenkins'?




--
View this message in context: 
http://jenkins.361315.n4.nabble.com/Mobile-provisioning-through-Jenkins-Xcode-Plugin-tp4645579.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

Reply via email to